xenodium/agent-shell

hmm, I haven't tried Carbon yet. But I have been using Argon on and off via agent-shell - https://github.com/xenodium/agent-shell and unofficial ACP client. In my limited usage, it has fixed issues which has not been correctly fixed by sol-6.1 (medium) - https://github.com/auto-gnufied/markdown-modern/commit/a189a06f157954e97f45e6b1e9b64a2a68acfdcd I am also using it via Google pro tier and did not immediately run into quota issues. But as someone else said in previous discussion of this - Google Pro tier already includes lot of stuff (including Youtube premium etc), the AI plans are just a nice addon.

Not who you replied to, but: I use agent-shell and I love the ecosystem that's being created there: https://github.com/xenodium/agent-shell And for claude interacting back with emacs: Some folks like having an MCP package. I agree that gives you a bit more control. But I live dangerously and run emacs in daemon mode and tell claude to just run emacsclient to execute elisp as needed. It works amazingly well. Claude has full visibility into my editor and together we can pretty much do anything. In fact, I increasingly think of emacs as just a live lisp machine. It's a surface that I and the agents can interact against. It acts as a document store, database, control surface, etc.

Not the person you're replying to, and I have no idea what they were referring to, but I use agent-shell.el and it is incredible: https://github.com/xenodium/agent-shell xenodium is doing some amazing work (and not just on agent-shell, either!)

I use it via the gnu emacs integration :P https://github.com/xenodium/agent-shell

Absolutely. I do all my LLM-assisted work inside Emacs using Agent Shell and Emacs skills: https://github.com/xenodium/agent-shell https://github.com/xenodium/emacs-skills

Never heard of that one. The most popular ways for agent stuff seems to be https://github.com/xenodium/agent-shell , or just opening a terminal in emacs and using claude code. If you want to run it through an emacs terminal, consider using https://github.com/dakra/ghostel#ghostel (or vterm, or eat)

You should give https://github.com/xenodium/agent-shell and https://github.com/dakra/ghostel a shot. With ghostel I genuinely mix up which window (frame) is emacs rather than the native Ghostty window.

It's not just Zed, Emacs has has a thriving ACP implementation in agent-shell[0], and allows for some very cool integrations[1]. There are a fair number of other clients[2] as well. [0]: https://github.com/xenodium/agent-shell [1]: https://www.youtube.com/watch?v=HJQ86HuSIJI [2]: https://agentclientprotocol.com/get-started/clients

…SONRPC (stdin/stdout) -> [ Agent subprocess (headless) ] > I'd love to know how that is wired to the agents; is that input sent over ACP? Yes. All traffic goes over ACP between Emacs and the agent. You can inspect the traffic using agent-shell itself. https://github.com/xenodium/agent-shell?tab=readme-ov-file#how-do-i-viewget-agent-client-protocol-traffic > Is that just sending to the shell? The compose buffer is an UX abstraction on top of the agent shell buffer which is a native Emacs buffer, but ultimately all traffic is sent over ACP. agent-shell's links to blog posts may be of interest https://github.com/xenodium/agent-shell?tab=readme-ov-file#news

As an aside: have you thought about using agent-shell? https://github.com/xenodium/agent-shell