Administration

scc stats

View and export usage statistics.

scc stats [OPTIONS]
scc stats export [OPTIONS]
scc stats aggregate [OPTIONS] FILES...

Options (main command):

Option	Description
-d, --days N	Filter to last N days

Subcommands:

stats export

Export statistics as JSON.

Option	Description
--json, -j	Output as JSON
--raw, -r	Export raw event data
-d, --days N	Filter to last N days
-o, --output PATH	Output file path

stats aggregate

Aggregate multiple stats files (for team leads).

Option	Description
-o, --output PATH	Output file path
FILES...	Stats files to aggregate

Examples:

View Stats

# View all-time statistics
scc stats

# View last 7 days
scc stats --days 7

Export

# Export as JSON
scc stats export --json

# Export last 30 days to file
scc stats export --days 30 --output stats.json

# Export raw events
scc stats export --raw --output events.json

Aggregate

# Aggregate team stats
scc stats aggregate team1.json team2.json --output combined.json

Note

Statistics include session counts, duration, and per-project breakdown. Data is stored locally at ~/.config/scc/stats/.

---

scc support bundle

Generate a diagnostic bundle for troubleshooting.

scc support bundle [OPTIONS]

Options:

Option	Description
-o, --output PATH	Output path for the bundle zip file
--json	Output manifest as JSON instead of creating zip
--pretty	Pretty-print JSON output (implies --json)
--no-redact-paths	Don’t redact home directory paths

What’s included:

• System information (platform, Python version)
• CLI configuration (secrets automatically redacted)
• Doctor output (health check results)
• Diagnostic information

Examples:

Basic

# Generate support bundle
scc support bundle

# Save to specific location
scc support bundle --output ~/Desktop/scc-support.zip

JSON Output

# Output manifest as JSON (no zip)
scc support bundle --json

# Pretty-print JSON
scc support bundle --pretty

Tip

The bundle is safe to share — all sensitive data (secrets, API keys, tokens, passwords) is automatically redacted.

---

scc prune

Remove stopped SCC containers.

scc prune [OPTIONS]

Options:

Option	Description
-y, --yes	Skip confirmation prompt
--dry-run	Preview what would be removed

Examples:

Interactive

# Show stopped containers and confirm removal
scc prune

Scripted

# Preview what would be removed
scc prune --dry-run

# Remove without confirmation (CI/scripts)
scc prune --yes

Caution

Only removes stopped containers. Running containers are never affected. Use scc stop first if you want to stop running containers.

Note

There’s also scc worktree prune for cleaning up stale git worktree entries — that’s a different command.

---

scc reset

Unified maintenance hub for cache, sessions, contexts, and configuration.

scc reset [OPTIONS]

Selection Options:

Option	Risk	Description
--cache	Safe	Clear cache files (~/.cache/scc/)
--contexts	Low	Clear work context associations
--exceptions	Medium	Reset all policy exceptions
--exceptions-expired	Safe	Only cleanup expired exceptions
--containers	Low	Prune stopped Docker containers
--sessions	Low	Prune old sessions (keeps newest 20 per team)
--sessions-all	Medium	Delete entire session history
--config	Medium	Reset configuration (requires re-setup)
--all	High	Factory reset - removes all SCC data

Execution Options:

Option	Description
--plan	Fast preview - show what would change
-n, --dry-run	Execute without writing (validates permissions)
-y, --yes	Skip confirmation prompts
--force	Required with --yes for factory reset
--no-backup	Skip backup creation
--continue-on-error	Don’t stop on first failure (for CI)
--json	Machine-readable output
--non-interactive	Fail if prompt needed

Examples:

Common Tasks

# Clear cache and contexts (quick cleanup)
scc reset --cache --contexts

# Cleanup expired exceptions only
scc reset --exceptions-expired

# Prune old sessions (safe defaults: 30d, keep 20)
scc reset --sessions

Interactive

# Open interactive maintenance menu
scc reset

# Preview what factory reset would do
scc reset --all --plan

CI/Scripting

# Non-interactive cache clear
scc reset --cache --yes

# Factory reset in CI (requires --force with --yes)
scc reset --all --yes --force

# JSON output for automation
scc reset --sessions --json

Note

You can also access maintenance from the TUI by pressing s for Settings & Maintenance.

Caution

Factory reset (--all) removes all SCC data including configuration, sessions, exceptions, and cache. You’ll need to run scc setup again after a factory reset.

---

scc completion

Generate shell tab-completion scripts.

scc completion SHELL

Supported Shells: bash, zsh, fish

Installation:

Bash

Add to ~/.bashrc:

eval "$(scc completion bash)"

Zsh

Add to ~/.zshrc:

eval "$(scc completion zsh)"

Fish

Run once:

scc completion fish > ~/.config/fish/completions/scc.fish

---

File Locations

File	Purpose
~/.config/scc/stats/	Usage statistics storage
~/.config/scc/config.json	User configuration
~/.cache/scc/	Cached data (safe to delete)

Run scc config paths to see all locations with sizes and permissions.