sidecar

"[LLM-generated code] is ultra-useful if you can close the loop between the LLM and the execution environment (with an “Agent” setup). There’s lots to say about this, but for the moment: it’s a semi-effective antidote to hallucination: the LLM generates the code, the agent scaffolding runs the code, the code generates errors, the agent feeds it back to the LLM, the process iterates." Okay, so who's doing this today and how? This question came up recently in the Aider discord and not many had a good answer. Aider is great but the SDK is weak and second-class, so interacting with the repl frustrates agent-dev. Sidecar (which can run independently of Aide IDE, not to be confused with Aider), https://github.com/codestoryai/sidecar/ is one agent that was mentioned. Many of that projects issues are auto-responded to by a PR-creating agent. Anyt

hmmm you are right, the ergonomics of providing context are more powerful in zed. Feedback taken, we will work on it. We implicitly take in all the diagnostics on the files https://github.com/codestoryai/sidecar/blob/e5408782a3bfa461...

Yup, I have. We also use tree-sitter for the smartness of understanding symbols https://github.com/codestoryai/sidecar/blob/ba20fb3596c71186... and also the editor for talking to the Language Server. What we found was that its not just about having access to these tools but to smartly perform the `go-to-definition` `go-to-reference` etc to grab the right context as and when required. Every LLM call in between slows down the response time so there are a fair bit of heuristics which we use today to sidestep that process.

you missed this one https://github.com/codestoryai/sidecar Sidecar: The AI brains Aide: https://github.com/codestoryai/aide the editor

hmm.... I do think it can be extended to work outside of just the VSCode environment. If you look at the sidecar side of things: https://github.com/codestoryai/sidecar/blob/ba20fb3596c71186... these are the main APIs we use On the editor side: https://github.com/codestoryai/ide/blob/0eb311b7e4d7d63676ad... These are the access points we need The binary is fairly agnostic to the environment, so there is a possibility to make it work elsewhere. Its a bit non trivial but I would be happy to brainstorm and talk more about this

yup! feel free to add the client support, you are on the right track with the changes. To test the whole flow out here are a few things you will want to do: - https://github.com/codestoryai/sidecar/blob/ba20fb3596c71186... (you need to create the LLMProperties object over here) - add support for it in the broker over here: https://github.com/codestoryai/sidecar/blob/ba20fb3596c71186... - after this you should be at the very least able to test out Cmd+K (highlight and ask it to edit a section) - In Aide, if you go to User Settings: "aide self run" you can tick this and then run your local sidecar so you are hitting the right binary (kill the binary running on 42424 port, thats the webserver binary that ships along with the editor) If all of this sounds like a lot, you can just add the client and I can also take care of the plumbing!

Yep! And AWS Bedrock gives you also plenty of other models on the back end, plus better control over rate limits. (But for us the important thing is data residency, the code isn't uploaded anywhere.) Is it ~just about adding another file to https://github.com/codestoryai/sidecar/blob/main/llm_client/... ? I could take a look too - another way for me to test Aide by working with it to implement this. :-) (https://github.com/pasky/claude.vim/blob/main/plugin/claude_... is sample code with basic wrapper emulating Claude streaming API with AWS Bedrock backend.)

Yes, it is! https://github.com/codestoryai/sidecar