Agent commands now have a concrete worktree boundary, so escapes get blocked with a clearer log line.
What's wrong with this entry?
Bash and shell execution paths now take an isolationRoot so the checks that keep agent commands inside their worktree have a concrete boundary to compare against.
isolationRootis resolved from the agent worktree, falling back to the session worktree path.- Used by the checks that block commands whose cwd escapes the isolation worktree, and those that redirect git into the shared checkout.
- Blocked commands log with
isolationRoot=in the message and reporttengu_agent_worktree_cwd_escape_blocked. - The field itself is new in this build.
isolationRoot
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.236
macOS sandbox re-applies read and delete denials inside writable folders
Both mention sandbox
-
v2.1.236
Sandbox proxy no longer writes to sockets that have gone away
Both mention sandbox
-
v2.1.236
IPv6 hosts through the proxy
Both mention sandbox