Status and logs

Inspect the server's resolved configuration and operational logs.

Host diagnostics

subshell-server status
subshell-server service status

The first command shows the configuration that a boot would resolve, including source layers, paths, tmux, and MCP diagnostics. It does not boot the server. Service status asks the manager about the installed service.

--json provides machine-readable output. Secrets are masked rather than returned in plaintext.

Browser diagnostics

Sign in as an administrator. In the server dashboard's sidebar, open Server Settings → Status for resolved locations or Server Settings → Logs for system output and the audit trail. The logs page separates system output from the audit trail.

For service-manager output on Linux:

journalctl --user -u subshell-server.service

The server's own log file is separate from service output. Its location is part of the installation's path information.

Debugging

Locate the active configuration with Files and paths before changing logging or retention environment values.

--verbose or SUBSHELL_VERBOSE=1 increases console detail. SUBSHELL_DEBUG_LOGGING controls additional file logging and is a separate setting.

Terminated pane logs default to 30-day retention; SUBSHELL_LOG_RETENTION_DAYS=0 disables that sweep. Running panes are not swept.

Next steps

See Audit log and Troubleshooting.