Overview
Every sandbox includes asandbox command for inspecting runtime state, discovering ports, and diagnosing issues. No credentials required.
Commands
| Command | Description |
|---|---|
sandbox status | Show runtime service status and resource usage |
sandbox ports | Show detected local ports and external URLs |
sandbox url <port> | Print the external URL for a specific port |
sandbox app | Show primary app port and common run hints |
sandbox doctor | Check installed runtimes and sandbox basics |
sandbox status
Output
app service shows waiting until you start a process on APP_PORT. This is normal.
sandbox ports
Output
sandbox app
Output
sandbox doctor
Output
Troubleshooting
sandbox: command not found
sandbox: command not found
The helper is installed during image build. Rebuild the toolbox image to get the latest version. As a workaround, check status files directly:
cat /tmp/devbox-status.json | jq .status.sandbox ports shows no ports
sandbox ports shows no ports
The port scanner runs every 10 seconds. Wait a few seconds after starting a service, then retry. Verify your service is listening:
ss -tlnp | grep LISTEN.Port shows but URL returns 502
Port shows but URL returns 502
Verify the service binds to
0.0.0.0 or 127.0.0.1, not a specific interface. Check sandbox status for service states.