CLI

Commands

Workflow-oriented guide to the main Sentinel commands, with links to the full CLI reference.

Start with one of these

sentinel docker Best first command for local multi-container development.
sentinel dev Best when you want Sentinel to supervise a configured multi-service dev stack.
sentinel run -- <command> Best first command when you own the process launch.
sentinel stdin Best when another command already produces the logs you want.
sentinel watch <glob...> Best when your app writes log files.

Docker workflow

Command	Purpose
`sentinel docker`	Start ingesting Docker logs with auto-discovery
`sentinel docker --all-running`	Ignore Compose auto-discovery and watch every running container
`sentinel docker list`	Show watched and ignored containers
`sentinel docker explain [container...]`	Explain selection behavior for one or more containers

Dev stack workflow

Command	Purpose
`sentinel dev init`	Create `.sentinel.yml` for the current repo via the wizard
`sentinel dev`	Start the selected service group and open the terminal UI
`sentinel dev --group <name>`	Start a named service group
`sentinel dev --attach-only`	Attach to already-running services; do not start command services
`sentinel dev --dry-run`	Print the resolved plan and exit without starting anything
`sentinel dev --yes`	Skip the preflight confirmation prompt
`sentinel dev status [--json]`	Show the active dev session state for this workspace
`sentinel dev stop [--force]`	Stop the active dev supervisor (`--force` after an 8s graceful timeout)
`sentinel dev doctor [--group <n>] [--json]`	Check Docker, Compose, and per-service binaries

For the full guide, including .sentinel.yml schema, TUI keybindings, redaction behavior, and OTLP injection, see Dev.

Issue workflow

Command	Purpose
`sentinel history`	List recent fingerprints/issues
`sentinel explain`	Inspect an issue in more detail
`sentinel investigate <fingerprint-prefix>`	Mark an issue as investigating
`sentinel resolve <fingerprint-prefix>`	Mark an issue as resolved
`sentinel suppress <fingerprint-prefix>`	Mute an issue from analysis
`sentinel unsuppress <fingerprint-prefix>`	Remove suppression
`sentinel check`	Check runtime configuration and environment
`sentinel analyze`	Re-run triage on unresolved or recent issues

UI, traces, and maintenance

Command	Purpose
`sentinel ui`	Start the local web UI
`sentinel traces`	List recent trace rows with filters
`sentinel trace <trace-id>`	Show a single trace and its spans
`sentinel project list`	List known projects
`sentinel project delete <project>`	Delete one project’s stored data
`sentinel update`	Update the installed binary from published releases
`sentinel version`	Print version information

Recommended starting points

Docker users: sentinel docker
Supervised local stack: sentinel dev
Local dev server: sentinel run -- npm run dev
Existing log command: docker logs -f api | sentinel stdin
File logs: sentinel watch ./logs/*.log
Inspect issues: sentinel ui
Inspect traces: sentinel traces

For exact syntax, flags, and examples, use the CLI reference.