Skip to main content

Documentation Index

Fetch the complete documentation index at: https://auto-sop.com/docs/llms.txt

Use this file to discover all available pages before exploring further.

status

Show the install status of auto-sop for a project — hooks, scheduler, managed section, and pause state.
auto-sop status [options]

Options

OptionDescription
--project <path>Project root (default: current directory)

Example

auto-sop status
auto-sop v0.0.66
Project: /Users/you/projects/my-app
Hooks:          ok
Scheduler:      ok
Managed section: ok
Paused:         no
Directives:     12 active

doctor

Run deep health checks on the auto-sop installation. Validates hooks configuration, scheduler registration, file permissions, and managed section integrity.
auto-sop doctor [options]

Options

OptionDescription
--project <path>Project root (default: current directory)

Example

auto-sop doctor
[ok] hooks registered in .claude/settings.local.json
[ok] hook shim executable and accessible
[ok] scheduler plist loaded and running
[ok] capture directory exists and writable
[ok] CLAUDE.md managed section present and hash-valid
[ok] no stale lockfiles detected
Run doctor after OS upgrades or if status reports issues. It performs deeper checks than status including file permissions and process state.

recent

Show recent Claude Code activity captured for the current project.
auto-sop recent [options]

Options

OptionDescription
--since <duration>Time window — e.g., 30m, 1h, 2h, 1d, 1w (default: 1h)
--project <path>Project directory (default: current directory)

Examples

auto-sop recent

show

Show full details of a specific turn or session by ID.
auto-sop show [options] <id>

Options

OptionDescription
--rawNo formatting, raw file dump
--filesOnly list files changed
--toolsOnly show tool-calls summary
--project <path>Project directory (default: current directory)

Examples

auto-sop show abc123
Get turn/session IDs from auto-sop recent output. Each captured interaction has a unique short ID.

errors

Show recent errors from the errors.jsonl log. Useful for debugging hooks, scheduler failures, or learner issues.
auto-sop errors [options]

Options

OptionDescription
--project <path>Project root (default: current directory)
--tail <n>Show last N entries (default: 20)
--since <duration>Only show entries since duration ago — e.g., 1h, 24h, 7d
--globalRead from global per-project mirror (~/.claude/sop/<hash>/errors.jsonl)

Examples

auto-sop errors
Start with auto-sop errors --since 1h when troubleshooting. If no local errors appear, try --global to check the global mirror.

stats

Show directive-fire metrics — how often each directive triggered, time saved estimates, and effectiveness rankings.
auto-sop stats [options]

Options

OptionDescription
--project <path>Project root (default: current directory)
--since <date>Filter fires after this date (ISO or YYYY-MM-DD)
--minutes-per-error <n>Minutes saved per error prevented (default: 15)

Examples

auto-sop stats
Use --minutes-per-error to calibrate time-saved estimates for your workflow. If your bugs typically take 30 minutes to fix, set it to 30 for more accurate ROI numbers.