From f32ec66383f8174ae195a1d20960ac4ba4c7426d Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Tue, 4 Aug 2026 11:10:29 +0000 Subject: [PATCH] docs: document sbx daemon restart Daemon restart guidance required separate stop and detached-start commands. Replace that sequence and related proxy guidance with sbx daemon restart.\n\nCo-Authored-By: Claude --- content/manuals/ai/sandboxes/architecture.md | 2 +- content/manuals/ai/sandboxes/troubleshooting.md | 3 +-- 2 files changed, 2 insertions(+), 3 deletions(-) diff --git a/content/manuals/ai/sandboxes/architecture.md b/content/manuals/ai/sandboxes/architecture.md index 7d0c8332f950..00993c06ea62 100644 --- a/content/manuals/ai/sandboxes/architecture.md +++ b/content/manuals/ai/sandboxes/architecture.md @@ -94,7 +94,7 @@ semantics. This only affects traffic routed through `DOCKER_SANDBOXES_PROXY` Set these variables in the environment where the sandbox daemon starts. The daemon starts automatically the first time a command needs it, so set the variables before you run a `sbx` command. If the daemon is already running, -restart it for a change to take effect. +run `sbx daemon restart` for a change to take effect. One limitation applies: diff --git a/content/manuals/ai/sandboxes/troubleshooting.md b/content/manuals/ai/sandboxes/troubleshooting.md index 7be080191a21..9205fe823599 100644 --- a/content/manuals/ai/sandboxes/troubleshooting.md +++ b/content/manuals/ai/sandboxes/troubleshooting.md @@ -28,8 +28,7 @@ If sandbox commands hang, fail to connect to the daemon, or keep returning daemon errors, restart the sandbox daemon before resetting sandbox state: ```console -$ sbx daemon stop -$ sbx daemon start --detach +$ sbx daemon restart ``` Then retry the command that failed. Restarting the daemon doesn't delete