From e60c54bdbd0b68afaa5bae70e1928d759b74c12d Mon Sep 17 00:00:00 2001 From: David Karlsson <35727626+dvdksn@users.noreply.github.com> Date: Fri, 20 Nov 2026 09:15:19 +0000 Subject: [PATCH] docs: explain how to view sandbox daemon logs The troubleshooting guide lacks a direct way to inspect daemon errors. Add examples for viewing recent daemon logs, changing the tail count, and following output while reproducing an issue. --- .../manuals/ai/sandboxes/troubleshooting.md | 21 +++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/content/manuals/ai/sandboxes/troubleshooting.md b/content/manuals/ai/sandboxes/troubleshooting.md index d354114de74..b4b19f6e369 100644 --- a/content/manuals/ai/sandboxes/troubleshooting.md +++ b/content/manuals/ai/sandboxes/troubleshooting.md @@ -76,6 +76,27 @@ $ sbx start Files saved in the sandbox are kept when you stop and start it. +## View daemon logs + +To investigate local daemon errors, show the last 100 lines of the daemon log: + +```console +$ sbx daemon logs +``` + +Use `--tail` to change the number of recent lines shown: + +```console +$ sbx daemon logs --tail 200 +``` + +To keep printing log lines while you reproduce an issue, use `--follow`. +Press Ctrl+C to stop following: + +```console +$ sbx daemon logs --follow +``` + ## Restart the sandbox daemon If sandbox commands hang, fail to connect to the daemon, or keep returning