Skip to content

sbx: describe sbx kit add as a sandbox restart, not a container recreation #25546

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

Merged
dvdksn merged 3 commits into from
Jul 14, 2026
+7 −6
Merged

sbx: describe sbx kit add as a sandbox restart, not a container recreation #25546

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
a992039
sbx: describe sbx kit add as a sandbox restart, not a container recre…
dvdksn Jul 13, 2026
4f351b1
docs: remove deprecated docker sandbox (Docker Desktop plugin)
dvdksn Jul 14, 2026
52690d5
Revert "docs: remove deprecated docker sandbox (Docker Desktop plugin)"
dvdksn Jul 14, 2026
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
13 changes: 7 additions & 6 deletions content/manuals/ai/sandboxes/customize/kits.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -316,8 +316,9 @@ $ sbx run claude --kit /path/to/ruff-lint/

To apply the mixin to a sandbox that's already running, use
[`sbx kit add`](#local) instead. The `--kit` flag only takes effect when a
sandbox is created. `sbx kit add` recreates the sandbox container, but VM state
— installed packages, Docker images, volumes, and agent history — is preserved.
sandbox is created. `sbx kit add` restarts the sandbox to apply the kit, but VM
state — installed packages, Docker images, volumes, and agent history — is
preserved.

## Sandbox kits

Expand Down Expand Up @@ -389,9 +390,9 @@ several kits on the same sandbox.
> against an existing sandbox name fails with
> `--kit can only be used when creating a new sandbox`. To extend a
> running sandbox with a kit, use [`sbx kit add`](#local) instead.
> `sbx kit add` recreates the sandbox container with the updated kit set.
> `sbx kit add` restarts the sandbox to apply the updated kit set.
> VM state — installed packages, Docker images, volumes, and agent history
> — is preserved across the recreation.
> — is preserved across the restart.

### Local

Expand All @@ -408,9 +409,9 @@ While iterating on a kit, apply changes to a running sandbox with `sbx kit add`:
$ sbx kit add my-sandbox ./my-kit/
```

`sbx kit add` recreates the sandbox container with the updated kit set.
`sbx kit add` restarts the sandbox to apply the updated kit set.
VM state — installed packages, Docker images, volumes, and agent history — is
preserved across the recreation. The kit's network allow/deny rules take effect
preserved across the restart. The kit's network allow/deny rules take effect
immediately. Kits can't be removed from a running sandbox — remove and recreate
it to start clean.

Expand Down