You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 342c0d4
Browse filesBrowse the repository at this point in the historyBrowse files
Copy file name to clipboardExpand all lines: docs/sdk/tools.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -451,11 +451,11 @@ Install the wheel and native helpers outside the workspace and any additional wr
451
451
452
452
Writes to host files are limited to `cwd` and the additional `writable_roots`. On Linux, a command can also write to a private temporary filesystem. Those writes disappear when the sandbox exits. The runtime resolves the paths on the executor. It keeps its protections for native metadata. For a linked Git worktree that needs to update Git state, explicitly grant the required Git directories after checking which paths they expose.
453
453
454
-
Pass `writable_roots` when constructing the local Environment or a compatible Linux or macOS WSS Environment. Passing it to the WSS constructor opts into the same strict write policy. The policy disables native sandbox escalation and permission requests that could widen the grants.
454
+
Pass `writable_roots` when constructing the local Environment or a compatible Linux or macOS WSS Environment. For WSS, pass a non-`None` sequence to enable the strict write policy. Use `writable_roots=[]` to grant writes only in the working directory. Passing `None` uses the default WSS policy. The policy disables native sandbox escalation and permission requests that could widen the grants.
455
455
456
456
Use a supported local executor or Linux WSS executor to change write grants between turns. With macOS WSS, choose the write roots in the Environment when opening the Session. The SDK cannot confirm that processes from earlier remote commands have exited. You can resubmit an equivalent grant if the paths pass validation.
457
457
458
-
In a Session without `NativeAgents`, wait for the active turn and any descendant or background executor work to settle. Collect the results of any yielded tool cells before changing the roots. Then supply the complete replacement list on the next root turn. If an active root uses a symlink, the path must still resolve to the same directory when you submit it again. When adding a directory to the current root list, pass the canonical executor path from your application's configuration. Use the same rule when restoring a grant you removed. If the Session uses `NativeAgents`, set its write roots when opening it.
458
+
In a Session without `NativeAgents`, wait for the active turn and any descendant or background executor work to settle. Collect the results of any yielded tool cells before changing the roots. Then supply the complete replacement list on the next root turn. If a current writable root uses a symlink, the path must still resolve to the same directory when you submit it again. When adding a directory to the current root list, pass the canonical executor path from your application's configuration. Use the same rule when restoring a grant you removed. If the Session uses `NativeAgents`, set its write roots when opening it.
0 commit comments