Skip to content

docs(acp): drop stale 'deferred to v0.2' from README header #87

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
rohitg00 merged 1 commit into from
May 6, 2026
Merged

docs(acp): drop stale 'deferred to v0.2' from README header #87

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions acp/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,9 +9,13 @@ and drive it through their native agent UI. No editor plugin, no fork, no
bespoke per-client integration.

> Status: 0.1.0. Server-side only (`acp-client` for consuming external ACP
> agents ships separately). Reverse-RPC paths (`session/request_permission`,
> `fs/*`, `terminal/*`) are deferred to v0.2 — internal iii brains use iii
> primitives directly for filesystem and terminal access.
> agents ships separately). All eleven client→agent methods are implemented
> (`initialize`, `authenticate`, `session/{new,load,resume,list,prompt,cancel,close,set_mode,set_config_option}`)
> plus the `session/update` agent→client notification. Reverse-RPC paths
> (`session/request_permission`, `fs/{read,write}_text_file`,
> `terminal/{create,kill,output,release,wait_for_exit}`) remain deferred —
> internal iii brains use iii primitives directly for filesystem and
> terminal access. Full per-method status in the [Methods](#methods) table.

## Why this exists (vs MCP, skills, agent workers)

Expand Down
Loading