Skip to content

Document ACP protocol research#608

Closed
AnthonyRonning wants to merge 1 commit into
masterfrom
codex-acp-support-maple
Closed

Document ACP protocol research#608
AnthonyRonning wants to merge 1 commit into
masterfrom
codex-acp-support-maple

Conversation

@AnthonyRonning

@AnthonyRonning AnthonyRonning commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • add a master Agent Client Protocol research doc for Maple ACP client support
  • document current ACP v1/v2 protocol state, stable and unstable method surfaces, transports, and capability negotiation
  • compare ACP support in Goose, OpenCode, and claude-agent-acp, with Maple-facing compatibility guidance

Validation

  • git diff --cached --check
  • rg scan for TODO/FIXME placeholders and non-ASCII drift before commit
  • opensecret-workspaces show acp-support

Open in Devin Review

Summary by CodeRabbit

  • Documentation
    • Added a detailed research note covering ACP v1 client protocol support, including protocol expectations, capability negotiation, session handling, permissions, tool calls, and compatibility considerations.
    • Included a comparison of multiple agents and transports, plus guidance on shared boundaries, initial capability support, and future test coverage.
    • Captured open questions and a research log for easier reference going forward.

@cloudflare-workers-and-pages

Copy link
Copy Markdown

Deploying maple with  Cloudflare Pages  Cloudflare Pages

Latest commit: bd3c5b0
Status: ✅  Deploy successful!
Preview URL: https://bd5c619b.maple-ca8.pages.dev
Branch Preview URL: https://codex-acp-support-maple.maple-ca8.pages.dev

View logs

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

Open in Devin Review

@coderabbitai

coderabbitai Bot commented Jul 8, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

Adds a single new documentation file, docs/agent-client-protocol-research.md, capturing ACP v1 protocol research: method/capability requirements, a compatibility matrix and details for Goose, OpenCode, and claude-agent-acp, plus Maple's architecture notes, capability plan, and a compatibility test plan.

Changes

ACP Research Documentation

Layer / File(s) Summary
Overview and protocol model
docs/agent-client-protocol-research.md
Documents executive takeaways, source inventory (Goose, OpenCode, claude-agent-acp snapshots), and the ACP v1 method/capability model including versioning, transport, lifecycle, cancellation, permissions, and config options.
Compatibility matrix and per-agent details
docs/agent-client-protocol-research.md
Adds a cross-agent compatibility matrix and detailed sections describing capability advertisement, transports, and idiosyncrasies for Goose, OpenCode, and claude-agent-acp.
Maple abstraction and architecture plan
docs/agent-client-protocol-research.md
Defines shared functionality priorities, cross-agent differences to abstract, an initial initialize capability plan, and Tauri/frontend ownership boundaries.
Test plan and open questions
docs/agent-client-protocol-research.md
Describes fixture-based and manual compatibility test plans, open questions on capability advertisement, and a running research log.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Poem

A rabbit hopped through JSON streams so wide,
Charting protocols with ACP as guide,
Goose, OpenCode, Claude — all inspected with care,
Notes for Maple stashed safely somewhere.
No code was hopped over, just docs in a row,
🐇📄 onward the research doth go!

🚥 Pre-merge checks | ✅ 4
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the documentation-focused change and summarizes the added ACP protocol research.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex-acp-support-maple

Comment @coderabbitai help to get the list of available commands.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@docs/agent-client-protocol-research.md`:
- Around line 48-66: The snapshot references in the research doc expose
workstation-specific /Users/admin checkout paths, including the repository
entries and the running log, so sanitize those identifiers everywhere they
appear. Update the research section and any related log text to use neutral
aliases or repo-relative labels instead of local filesystem paths, keeping the
repository names, snapshot commits, and file lists intact. Refer to the Goose
and agent-client-protocol snapshot entries in the doc so the replacements stay
consistent across the repeated sections.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 11b8e4ae-2208-4950-ba77-9d4281090cae

📥 Commits

Reviewing files that changed from the base of the PR and between 58fa0f3 and bd3c5b0.

📒 Files selected for processing (1)
  • docs/agent-client-protocol-research.md

Comment on lines +48 to +66
- Repository: https://github.com/agentclientprotocol/agent-client-protocol
- Local snapshot: `/Users/admin/repos/ThirdParties/agent-client-protocol`
- Snapshot commit: `dbe946b docs: update registry agents (#1628)`
- Key files:
- `README.md`
- `schema/v1/meta.json`
- `schema/v1/meta.unstable.json`
- `schema/v2/meta.json`
- `schema/v2/meta.unstable.json`
- `docs/protocol/v1/*.mdx`
- `docs/protocol/v2/*.mdx`

Goose:

- Repository: https://github.com/aaif-goose/goose
- Local snapshot: `/Users/admin/repos/ThirdParties/goose-upstream`
- Snapshot commit: `6d69936 chore: Remove stale crates/goose-server and update docs (#10224)`
- Also present: `/Users/admin/repos/goose-v1.39.0` is a dirty existing checkout
and was not modified.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔒 Security & Privacy | 🟠 Major | ⚡ Quick win

Redact the local checkout paths.

The /Users/admin/... paths leak workstation-specific details and make the doc hard to reuse. Replace them with sanitized aliases or repo-relative identifiers, including the same entries in the running log.

♻️ Example sanitization
- - Local snapshot: `/Users/admin/repos/ThirdParties/agent-client-protocol`
+ - Local snapshot: `<local checkout>/agent-client-protocol`

Also applies to: 82-106, 1279-1286

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@docs/agent-client-protocol-research.md` around lines 48 - 66, The snapshot
references in the research doc expose workstation-specific /Users/admin checkout
paths, including the repository entries and the running log, so sanitize those
identifiers everywhere they appear. Update the research section and any related
log text to use neutral aliases or repo-relative labels instead of local
filesystem paths, keeping the repository names, snapshot commits, and file lists
intact. Refer to the Goose and agent-client-protocol snapshot entries in the doc
so the replacements stay consistent across the repeated sections.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant