All our binaries are listed out here: https://github.com/codestoryai/binaries/releases/tag/1.94.2....
We're building Aide, an AI-native, privacy-first IDE. With the advent of AI, we believe there is an opportunity and necessity to re-imagine the IDE to be a place where developers and AI are both first-class citizens, and AI can pair-program as well as complete tasks independently.
We're still a team of 2, and are looking for a founding engineer with hands-on experience working with LLMs beyond basic prompting. ML background is not required, as long as you have understood LLMs deeply. We're not looking to train our own models, except fine-tuning when required for special use-cases. So someone who can understand and get into the internals of LLMs, hosting models, optimising model inference for our use case, setup evals, and (this may not be a skill you already have) can power the backend for streaming requirements needed to build agents in the next few years.
If this sounds interesting, apply at https://www.workatastartup.com/jobs/65502, and we'll get back to you shortly!
I'm Naresh, co-founder at CodeStory (YC S23) where we're building an AI-powered mod of VSCode. Though we're still in our very early days, we have some thoughts about how the IDE can evolve to be a space where developers can leverage agents as additional developers who can do complete end-to-end development. But we're getting there by exposing all the capabilities to developers interacting with the IDE as well as the AI agent.
One of the problems we wanted to tackle first was code search within an IDE and ways to augment it to be a much more powerful experience. I'd love to hear your thoughts on the approach, feedback or open discussions about what we've built and how you'd like to see this evolving!
AI could provide some different views of project structure (not file/folder). AI could use existing IDE tooling?
None of this is a reimagining of the IDE, just some incremental additions to it.
That being said, this is not accidental because we intend to not fundamentally disrupt the core workflows of today right away (as another comment said — IDEs of today are indeed built on years of user experience research). But we do see the capability to simplify or rethink the developer experience once AI is deeply integrated into every workflow. Its perhaps the same way I'd have never stated writing code as a problem, but after having used Copilot, I don't want to go back to not having it.