Repository navigation
feat(sandbox): auto-approve permissions inside sandboxes - #210
Merged
Merged
Conversation
The injected guest config now always carries permission: "allow" (and is injected even without a gateway login — providers skip the broker when the route table is empty). Everything the agent does is confined to the VM and the one mounted project folder, so prompts buy nothing there; the server stops asking, and the app's existing enableConfiguredDirectory seam surfaces it as directory auto-accept, which the user can still toggle off and a project config can override (project merges after CODEV_CONFIG). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This was referenced Aug 13, 2026
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.
Phase 4b, item 1 — the CoWork "hand it a task and walk away" default.
How
No new UI or permission code: the guest config injected via
CODEV_CONFIG(from #209) now always carries top-level"permission": "allow", and is injected even when there's no gateway login (providers start a broker only when the route table is non-empty). That one field does the whole job on both sides:"allow"to{"*": "allow"}and stops asking — enforcement, not UI sugar.enableConfiguredDirectoryseam seespermission: "allow"on the sandbox server's directories and switches on directory-level auto-accept in the UI, exactly as it already does for any server so configured — and it respects prior manual state, so the user's per-directory toggle still wins.permissionblock in the workspace's own project config (project config merges afterCODEV_CONFIG).Safety framing: inside a sandbox the blast radius is the VM plus the one mounted project folder, which is what makes auto-allow the right default there and nowhere else.
Tests
CODEV_CONFIG+ host-side file) and starts no broker (no socat line).Note for the next in-app run: a fresh sandbox session should execute shell/edit tools without a single permission dialog, and the directory row should show auto-accept enabled.
🤖 Generated with Claude Code