Skip to main content
Use a writable mount when an agent needs to create or edit files. The mount gives the sandbox an ephemeral directory, such as /work. Files written to the mount become durable when you snapshot them into the workspace behind it. The default mode is private: snapshots stay isolated until you promote them.

​
Mount a Writable Directory

/work is now an ordinary writable directory. The workspace starts from main, but the branch does not change while the agent is editing files.

​
Snapshot Changes

Snapshotting persists the current /work file state as a commit on the workspace. Snapshotting with no changes is a no-op:

​
Promote to a Branch

By default, promotion publishes one clean commit to the target branch. Future agents that mount that branch, and Git users who clone or fetch it, get that version. Following read-only mounts pick up the update automatically. Activity history shows who published the promotion and which workspace it came from. Use --full-history when you want every workspace snapshot to land as its own commit:

​
Shared Read-write Mounts

Use --shared-rw when every snapshot should publish to the target branch automatically.
This mode is for fleets that cannot wait for a manual promotion step. It requires a branch target and is incompatible with --mode ro.

​
Next Steps

Manage Workspaces

Inspect dirty files, reattach, clean up, diff, and restore.

Architecture

Learn how promotion and merge conflict handling work internally.