Skip to content

docs: clarify clone mode security boundary #25655

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
devendrakushwah80 wants to merge 1 commit into
base: main
Choose a base branch
from
+8 −3
Open

docs: clarify clone mode security boundary #25655

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
11 changes: 8 additions & 3 deletions content/manuals/ai/sandboxes/security/isolation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -148,6 +148,13 @@ never works directly against your host repository. Even with full root
inside the VM, it cannot modify your `.git` directory, your working tree,
or any tracked file on your host.

> [!IMPORTANT]
> Clone mode protects your host repository from modification, **not from
> inspection**. Your repository is still mounted read-only into the sandbox,
> including untracked files and files excluded by `.gitignore`. Files such as
> `.env` remain readable by the agent. Store secrets outside your working
> directory or use [credential isolation](credentials.md) instead.

```mermaid
flowchart LR
subgraph host["Host repository (untouched)"]
Expand All @@ -174,9 +181,7 @@ How the boundary is enforced:
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.
credential files not tracked by Git, such as `.env`.
- 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