I'd also written an analysis of the code - including announcing a $1000 prize for the best alternative code: https://ai88.substack.com/p/ceiling-has-been-raised-analyzin...
We were going to announce the winner this week but if we get a few more submissions we will definitely consider them.
Just submit a PR to https://github.com/CopilotKit/CopilotKit
Your tweet at https://twitter.com/ataiiam/status/1765089261374914957 mentions "Cursor's copilot".
The blog post at https://rtpg.co/2024/03/07/parsing-copilots-type-spaghetti/ talks about GitHub Copilot - did they make a mistake there?
And your product is CopilotKit - is that related to the GitHub and Cursor Copilots in some way or is it something different?
We are building CopilotKit = a framework + platform for building context-aware AI assistants into any application (not necessarily coding related applications).
Part of CopilotKit is about giving the Copilot / AI agents access to the application through a typed "inline realtime API". And to make ergonomics great for _our_ users, CopilotKit ships with hardcore type programming.
Cursor's Copilot (unrelated to CopilotKit) helped us write this type code (that's what went viral). And yes, GitHub Copilot is a mis-attribution.
What ideas do you think are still missing from today's Copilots?
I.e. suppose we were looking back at today's Copilots 5 years from now- besides better models, what else has changed?