Repository navigation
fix(buzz-acp): accept write route policies on the shared backend - #8
Merged
kombiz merged 2 commits intoOct 11, 2026
Conversation
HS-46's owner chose full task agents on secrets.ts, so the Buzz routes will declare repository_write/workspace_write. The shared backend now accepts every valid profile and side-effect class and refuses only unknown values at startup; the daemon still checks the exact route match. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Review follow-up. The shared backend cancels every permission request, so a write route can edit files only when the gateway's agent command already runs without prompts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
kombiz
merged commit Oct 11, 2026
850a912
into
task/BUZZ-ACP-0524/gateway-acp-on-v0-5-24
64 checks passed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
HS-46 follow-up to #3.
Why: #3 limited
backend=sharedto read-only declarations. The owner has since chosen full task agents for the two secrets.ts resident agents, so their routes will berepository_write/workspace_writewith the gateway's host write opt-in. Read-only validation would refuse that configuration at startup.What:
BUZZ_ACP_GATEWAY_PERMISSION_PROFILEnow acceptsrepository_read,repository_writeorrestricted.BUZZ_ACP_GATEWAY_SIDE_EFFECT_CLASSacceptspure_read,external_effectsorworkspace_write. Only unknown values fail at startup. The daemon still refuses any submit that does not match the admitted route exactly, and the legacy backend still rejects these options. The test and README are updated to match.Checks on cachy:
cargo fmt --check,cargo clippy -p buzz-acp --all-targets -D warningsandcargo test -p buzz-acp(980 passed) all pass.Nothing is deployed.
🤖 Generated with Claude Code