Logging

Every sandbox writes its output to plain-text log files on disk. You can view, stream, and download these logs through the CLI, the dashboard, or the MCP plugin.

Log Storage

Logs are stored per-sandbox at:

~/.stackie/storage/logs/{sandbox_id}/
  stdout.log   # standard output
  stderr.log   # standard error

Log files are newline-delimited plain text. They are never rotated during a sandbox’s lifetime but are removed when the sandbox is destroyed.

Docker Compose Logging Compatibility

When Docker-compatible tools target Stackie’s socket, Stackie deliberately ignores Docker Compose logging: driver options such as json-file, fluentd, syslog, gelf, or cloud log drivers. Those options configure Docker daemon routing for container stdout/stderr. Stackie is the runtime, so it captures every sandbox process’s stdout and stderr centrally into the files above instead of forwarding them to Docker logging backends.

If an application writes only to its own file path, the block definition is responsible for configuring that application to write under a Stackie-managed log path or to stdout/stderr. Stackie does not parse or rewrite arbitrary user-provided shell redirections.

Viewing Logs

# Stream live logs for a running sandbox
stackie logs <sandbox>

# Show the last 50 lines
stackie logs <sandbox> --tail 50

# Follow log output in real time
stackie logs <sandbox> --follow

Error Detection

Stackie automatically scans log output for error patterns and classifies lines by severity (info, warning, error, fatal). Errors surfaced in the dashboard and CLI originate from this analysis.