ACP support would be a big deal and would make this a real contender for me. It looks super nice, but the idea of re-writing my Pi plugins is a real blocker.
I’m generally happy with my agent and want to keep that, but I do think the UI could be better and this looks like a neat step that way.
I guess there are 2 sides of ACP that are valid then. What was asked is for Juggler to act as a ACP client. I, on the other hand, would appreciate it to be a ACP server, so that I can interact with it from my editor when I’m on my machine and from the web when on the go or for more advanced functionality. That’s my current approach with opencode.
This seems like an odd request to me, but maybe I'm misunderstanding what you want or what Juggler does.
To my understanding, Juggler is a frontend to your agent and would replace your editor. That's the selling point I got, a better UI than text for orchestrating your agents.
ACP servers are agents (like if you look at the spec you have to implement an entire agent's worth of endpoints, from creating sessions and sending messages to handling starting MCP servers the client specifies).
I don't get the sense that the point of Juggler is to make the world's best agent (rather it's to make the world's best interface to agents), but OP would know way better than me.
What you're describing sounds like an ACP proxy, which probably exists but is a different class of thing.
If you just want to drive OpenCode via Juggler rather than your text editor, you also want Juggler to be an ACP client (it can be both an HTTP server and ACP client, I have some stuff at home that does that).
Connecting to juggler remotely from a browser is baked into its whole architecture! The entire GUI is identical in the desktop app or browser, local or remote. So I'm not really sure I see much point in making it a server. But as a client, sure, will add that.
I’m generally happy with my agent and want to keep that, but I do think the UI could be better and this looks like a neat step that way.