CL-9362: resolve restricted-worktree carve-out for agentId-targeted fleet calls - #1184
Merged
TheGreatAxios merged 4 commits intoSep 27, 2026
Conversation
TheGreatAxios
changed the base branch from
cl-8987-auto-mode-still-asks-on-fleet-continuation-tools
to
main
September 27, 2026 22:29
Name resume_agent and read_agent_trace in the agentId carve-out so all five single-target verbs are explicit, and build the CL-9362 gate on a registered worktree with a session-state control write that still asks.
…rve-out pin The previous fixture registered cwd as a root, which is the in-bounds pattern, and the session-state write control already lives in its own test. The alwaysRestricted classify loop is the real pin.
TheGreatAxios
force-pushed
the
cl-9362-resolve-restricted-worktree-carve-out-for-agentid-targeted
branch
from
September 27, 2026 22:32
24b4b15 to
84e9048
Compare
TheGreatAxios
enabled auto-merge (squash)
September 27, 2026 22:33
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
1 participant
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.
Stacks on #1168 (base:
cl-8987-auto-mode-still-asks-on-fleet-continuation-tools); merge after it lands.CL-9362 decision: agentId-to-worktree resolution does NOT belong in
callTargetsRestricted. The vacuous!restrictedcarve-out forclose_agent/interrupt_agent/send_input/resume_agent/read_agent_traceis intentional — these verbs address workers by opaque agent id, never by path, so there is nothing path-shaped forisRestrictedto judge. Path restriction is enforced where paths are actually touched: inside the target worker, whose own gate binds restriction judgments to its process cwd. Resolving ids to worktrees in classify would duplicate that enforcement at a layer with no session access.Pinned by a regression test: the five agentId-targeted fleet verbs auto-allow in auto mode, and
callTargetsRestricted(..., alwaysRestricted)stays false. The same-gatewrite_file("notes.md")control is an in-bounds auto-allow so the fixture cannot be read as a restricted worktree.Fixes CL-9362