IssueRaiser

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) —

Posted by Joseph19820124 on May 20, 2026, 3:58 AM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

github (Sysadmin)

Feature request: add ACP (Agent Client Protocol) stdio JSON-RPC mode

Joseph19820124May 20, 2026, 3:58 AM

## 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) —

Comments (0)

No comments yet. Start the discussion.

Comment on this issue