Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 7 additions & 2 deletions content/manuals/ai/sandboxes/security/isolation.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,8 +165,13 @@ flowchart LR
How the boundary is enforced:

- Your repository's Git root is mounted at `/run/sandbox/source` as
read-only. Nothing the agent does inside the VM can write back through
that mount.
read-only. The mount covers your entire working directory, including
untracked files and files excluded by `.gitignore`. Nothing the agent
does inside the VM can write back through that mount, but all files
under the Git root are readable inside the sandbox. This includes
credential files not tracked by Git, such as `.env`. Store
secrets outside your working directory or use
[credential isolation](credentials.md) instead.
- The agent works on a private clone that lives inside the sandbox. The
clone has its own index, its own refs, and its own working tree. Writes
to the clone never reach your host.
Expand Down
7 changes: 4 additions & 3 deletions content/manuals/ai/sandboxes/usage.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,9 +99,10 @@ same time, they may step on each other's changes — use

### Clone mode

In clone mode, the sandbox becomes a Git remote on your host. The agent
commits inside the sandbox; you pull its work back out by fetching from
that remote.
In clone mode, the sandbox becomes a Git remote on your host. Your entire
working directory, including untracked files and files excluded by `.gitignore`, is mounted
read-only inside the sandbox. The agent commits inside the sandbox; you pull its work back
out by fetching from that remote.

> [!NOTE]
> Clone mode was introduced in `sbx` v0.31.0 and replaces the `--branch`
Expand Down