Skip to content

buzz-acp: report startup permission outcomes and capture returned state #7487

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

Open
p4jrj4b9nh-lab wants to merge 1 commit into
base: main
Choose a base branch
from
+255 −62
Open

buzz-acp: report startup permission outcomes and capture returned state #7487

Show file tree
Hide file tree
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
13 changes: 13 additions & 0 deletions crates/buzz-acp/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,19 @@ Buzz Relay ──WS──→ buzz-acp ──stdio──→ Your Agent

Supports any agent that speaks [ACP](https://agentclientprotocol.com/) over stdio: **goose**, **codex** (via [codex-acp](https://github.com/agentclientprotocol/codex-acp)), and **claude code** (via [claude-agent-acp](https://github.com/agentclientprotocol/claude-agent-acp)).

## Startup permission diagnostics

Startup emits a `pool::permission` log and a `startup_permission_mode_outcome`
observer frame with the requested wire ID, adapter-advertised IDs, and outcome:
`default`, `skipped_unsupported`, `applied`, `rejected`, `failed_transport`, or
`timed_out`. Unsupported IDs are never translated to broader modes. `applied`
means the adapter accepted the RPC, not that its downstream policy was verified.

The subsequent `session_config_captured` frame uses the successful permission
response's options, modes, and models; omitted fields are unknown (`null`), not
copied from before the mutation. These frames do not establish the provider's
reviewer, sandbox, command-rule sources, or a narrow operation grant.

## Prerequisites

- A running Buzz relay (`just relay` starts Docker services automatically, or use a hosted instance)
Expand Down
Loading