SaaS Metrics
GitHub Issue
Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode
## Summary
Please add an `--acp` (or equivalent) flag that runs `agy` as a JSON-RPC-over-stdio agent server, matching the [ACP](https://github.com/zed-industries/agent-client-protocol) shape that `gemini-cli --acp`, `claude --acp`, `cursor-agent acp`, `codex acp`, etc. already implement.
## Background
`agy` v1.0.0 currently exposes only:
| Mode | Streaming output | Tool approval | Cancel | Conversation state |
|---|---|---|---|---|
| Default TUI | ✅ | ✅ | ✅ | ✅ |
| `-i / --prompt-interactive` | ✅ | ✅ | ✅ | ✅ |
| `-p / --print` | ❌ (single block) | ❌ (skip-permissions only) | ❌ | New each invocation |
None of these can be driven programmatically by an external orchestrator that needs to:
- Receive incremental `agent_message_chunk` / `agent_thought_chunk` events as the model streams
- Pause mid-turn for human approval on destructive tool calls
- Send a `session/cancel` notification mid-stream
- Resume an existing session across separate orchestrator invocations
## Use cases impacted
There is a substantial ecosystem of orchestrators that spawn coding-agent CLIs as ACP-stdio subprocesses to bridge them into chat platforms (Discord, Slack, MS Teams), schedulers, and remote/headless workflows. Examples:
- [openabdev/openab](https://github.com/openabdev/openab) — Discord/Slack ↔ coding agent bridge (484 stars). Already supports Claude Code, Gemini CLI, Codex, Cursor, Copilot, Grok, Hermes, OpenCode — all via `--acp`.
- [sst/opencode](https://github.com/anomalyco/opencode) —...
View Raw Thread
Developer & User Discourse
sbinnee • May 20, 2026
I want ACP too because Gemini CLI supported it too. But this OP content is AI-generated... As far as I know, Claude Code `claude` and `codex` DO NOT support ACP in fact. Their ACP implementations are provided by JetBrains and Zed teams.
myoung3 • May 20, 2026
Absence of ACP in antigravity-cli means [agent-shell ](https://github.com/xenodium/agent-shell) won't have a gemini option after gemini-cli is deprecated.
Agent-shell is an agent-agnostic front-end to tools like gemini-cli and claude code designed to make terminal based code assist tools easier to use in emacs. There are a lot of issues with running antigravity-cli/claude code/gemini-cli directly in vterm in emacs.
Agent-shell is an agent-agnostic front-end to tools like gemini-cli and claude code designed to make terminal based code assist tools easier to use in emacs. There are a lot of issues with running antigravity-cli/claude code/gemini-cli directly in vterm in emacs.
lmtr0 • May 21, 2026
+1 for acp support.
Currently I use the acp clients to develop projects in the background, this is crucial for it to work
Currently I use the acp clients to develop projects in the background, this is crucial for it to work
jimmyliao • May 21, 2026
+1 from a GDE perspective.
Concrete signal beyond the general ecosystem argument:
- I run a dual-engine workflow (Claude + Gemini) across ~10 machines
via Tailscale, using ACP brokers (OpenAB-style) to bridge them into
Discord/Telegram for mobile/remote use. `gemini --acp` is currently
the Gemini side of this; `agy --acp` would let it survive the 6/18
gemini-cli sunset without code changes on the orchestrator side.
- Re: sbinnee's correction — agreed, `claude --acp` is via
@zed-industries/claude-code-acp not native, and `codex acp` is via
Zed similarly. But the user experience is the same: a single
`--acp` invocation point. Whether agy ships it natively or Google
publishes an `@google/agy-acp` adapter, either resolves the
orchestrator integration gap.
Happy to test a beta if/when there's something to try.
Concrete signal beyond the general ecosystem argument:
- I run a dual-engine workflow (Claude + Gemini) across ~10 machines
via Tailscale, using ACP brokers (OpenAB-style) to bridge them into
Discord/Telegram for mobile/remote use. `gemini --acp` is currently
the Gemini side of this; `agy --acp` would let it survive the 6/18
gemini-cli sunset without code changes on the orchestrator side.
- Re: sbinnee's correction — agreed, `claude --acp` is via
@zed-industries/claude-code-acp not native, and `codex acp` is via
Zed similarly. But the user experience is the same: a single
`--acp` invocation point. Whether agy ships it natively or Google
publishes an `@google/agy-acp` adapter, either resolves the
orchestrator integration gap.
Happy to test a beta if/when there's something to try.
markgerrard • May 22, 2026
+1 for ACP support I currently use Gemini CLI ACP and Codex App Server as part of a human in the loop Claude Code Opus orchestration multi-agent bridge. AGY CLI not supporting it means reverting to a print bridge which will still work for code reviews but seriously limit any longer running jobs by not providing feedback.