Skip to main content
September 16, 2026 · GitHub release · All changes
Release entries start here. Earlier updates remain in the weekly archive.

​
Snapshots and branching

Save running work. Full snapshots capture a local sandbox’s disk, memory, and running processes so you can resume from a checkpoint:
Try several paths from one starting point. Branch a running or paused sandbox into independent copies, including several children at once. Copies share unchanged memory while keeping their writes private. You can also pause and resume a sandbox without saving a snapshot. Organize and move checkpoints. Snapshot groups, portable .msb archives, and incremental exports make saved work easier to manage. Disk-only snapshots now support running and paused local sandboxes; the SDK also adds cloud disk snapshots and restore through a compatible service. Full snapshots, branching, groups, and archives are local-only. See Snapshots for commands and requirements.

​
More features

  • Storage that follows your sandbox. Owned volumes survive restarts and become private copies in snapshots and branches. Root disks can grow without restarting, sealed layers can be compacted, and flat roots gain snapshot and pre-boot patch support. Volumes · Disk maintenance
  • More precise secret policies. Control where credentials are substituted, where placeholders may pass unchanged, and how violations are handled. Real credentials stay on the host. Secrets
  • Network controls and diagnostics. Set TCP and UDP connection limits independently, and trace startup and connection timings with optional profiling.

​
Improvements and fixes

  • New msb sandbox and msb sbx command groups retain familiar top-level commands.
  • Faster agent I/O through separate control and bulk-data paths, with shared-memory transport for supported local Unix SDK connections.
  • Disk-backed temporary storage and faster reclamation of completed TCP connections.
  • Stale handles can no longer reach a replacement sandbox with the same name.
  • Fixed macOS bind-mount truncation and TLS hostname panics; added standard stream paths and support for older metrics registries.
  • Cloud requests tolerate unknown network and runtime fields while validating known settings. New settings still require server support.

​
Before upgrading

Moving from v0.6? Follow the v0.7 migration guide, targeting v0.7.3 or a later compatible patch release.
  • Set up the runtime first. Sandbox creation no longer downloads it automatically. SDK setup APIs and Rust build features have changed. Runtime setup
  • Migrate secret policies. v0.7.3 migrates saved policies automatically; application code and configuration files may need changes. See secret policy migration.
  • Reconnect external resources. Restore and branch need explicit host mounts, published ports, and custom vsock routes. Snapshots do not copy host files or restore external connections. Use compatible runtime and firmware versions.
  • Choose shutdown timeouts. Graceful stop has no default deadline. A timeout does not force-kill the sandbox; killing requires an explicit request.
  • Review network limits. Defaults are unlimited for single-tenant sandboxes and 1,024 each for TCP and UDP in multi-tenant sandboxes. Zero means unlimited. maxConnections remains a deprecated TCP-only alias.

​
New guides

Get started with Browser Use or VS Code. The API reference now also covers personal tokens.