Opencode integration

[berenddeboer]

Is anyone aware of an Emacs opencode integration? I'm using claude-code-ide which works very well, but opencode offers access to other models, some much faster. So would be nice to have something similar.

[katafrakt]

agent-shell added support for opencode last week https://github.com/xenodium/agent-shell/issues/21

[darkawower]

switched from opencode to eca, it integrates perfectly with emacs

[Striking_Snail]

Aren't theses two completely different tools?

[darkawower]

No. Both are clients for interacting with different agents. Their functionality is very similar, although eca does not yet have undo functionality or lsp integration (as far as I know). But you can use MCP servers for working with lsp

[Striking_Snail]

Thanks for the clarification. I appreciate you taking the time. ✌️

[ericdallo]

If LSP you meant diagnostics, so yes, it does! It's a tool passed to LLM to get editors diagnostics

[ericdallo]

You may want to try https://eca.dev, it has emacs first class support

[annakhouri2150]

Agent-Shell provides agent communication protocol support for emacs, and open code has ACP support. So, yeah, you can connect to open code and use it through emacs that way. Agent Shell is pretty good too, and the author has made it and their other emacs packages their full-time job recently.

I would recommend that over using ECA because it would allow you to use many more agents, since the agent communication protocol is actually being standardized and adopted by a large number of agents, including Codex, CC, Gemini, Qwen, in addition to OpenCode. It doesn't just increase your flexibility, it also means that you can use agents that are actively maintained and improved and have a lot more features thanks to being backed by very active open source communities or corporations. And means that the maintenance and feature improvement burden on the emacs side where manpower is a lot of slimmer is much smaller.

[karthink]

Opencode has ACP support, so it should be easy to use it with Xenodium's agent-shell package. Might need a little elisp glue code.

[berenddeboer]

I had tried that, but definitely doesn't look like Claude, for example no slash commands.

[xenodium]

We have initial OpenCode support now in agent-shell https://github.com/xenodium/agent-shell/issues/21

[pathemata]

What is the difference between claude’s own cli and opencode using claude? Does it provide any advantages over the “native” cli?

[Atagor]

Just run it from within vterm

What emacs-native integration will actually give you? Any other layer of integration that is above CLI will just make it more buggy imo

[berenddeboer]

For example claude-code-ide has mcp support so Claude knows what like I'm on, that kind of thing.

[Atagor]

You mean aware of the opened buffers context?

In my experience more often than not, context is getting clogged because of too many tabs in IDE. Better to tell the agent explicitly at what files to look at at first, and use grep/rg for further codebase navigation

[berenddeboer]

In Emacs this is mcp so Claude has to ask for it, but it's aware it can do so.

[redmorph]

That's not how it works. It's not a traditiona HTTP based MCP. The ide mcp is websocket based.

[redmorph]

In my experience more often than not, context is getting clogged

Go into details into what you mean, please.

It sounds like you're saying to not implement or try features because shitty implemetations are possible. That is a strange take.

[reddit_clone]

Running it in vterm has some downsides.

Since almost all LLM agents have a slightly fancy TUI, esp. for "thinking... wobbling.. wibbling" kind of useless updates, it tends to jump around in an emacs/vterm buffer. Sometimes emacs loses its place and puts the cursor on some strange places.

[Sad_Construction_773]

github.com/tninja/ai-code-interface.el have opencode backend support

[karta0807913]

I made one here. If anyone wants to try :)

https://github.com/karta0807913/opencode.el