Skip to content

Config Commands

Manage SCC configuration.

Terminal window
scc config [ACTION] [KEY] [VALUE] [OPTIONS]

Actions:

ActionDescription
set KEY VALUESet a configuration value
get KEYGet a specific value
showShow all configuration
editOpen config in editor
explainExplain effective configuration with sources
validateValidate .scc.yaml for this workspace
pathsShow file locations with sizes and permissions

Options:

OptionDescription
--showShow current config
--editOpen config in editor
--field FIELDFilter explain output
--workspace PATHWorkspace path for project context
--team TEAMTeam profile to use for explain/validate
--jsonOutput explain/validate as JSON envelope

Examples:

Terminal window
# Show current configuration
scc config show
# Explain where settings come from
scc config explain
# Explain specific field
scc config explain --field plugins
# Validate project config in the current workspace
scc config validate
# Validate with a specific team
scc config validate --team backend
# Edit configuration
scc config edit

Shows the effective configuration with source tracking, enforcement status, and warnings:

Enforcement Status
Plugins: Enforced
network_policy: Partially enforced
Plugins
✓ scc-safety-net@sandboxed-code-official (from org.defaults)
✓ gis-tools@internal (from team.urban-planning)
✓ project-linter@internal (from project)
Blocked Items
✗ malicious-plugin@internal (blocked by pattern 'malicious-*' from org.security)
Denied Additions
⚠ some-server (requested by project: team not delegated)

For machine-readable output:

Terminal window
scc config explain --json

JSON includes data.blocked_items and data.denied_additions for automation.

Validates project config (.scc.yaml) against team/org policy gates and reports blocked or denied additions.

Terminal window
scc config validate --team backend

Show all SCC file locations with sizes and permissions.

Terminal window
scc config paths [OPTIONS]

Options:

OptionDescription
--jsonOutput as JSON
--show-envInclude XDG environment variables

Example output:

SCC File Locations
────────────────────────────────────────────────────────────────────
Config ~/.config/scc/config.json 2.1 KB ✓ exists rw
Sessions ~/.config/scc/sessions.json 4.2 KB ✓ exists rw
Exceptions ~/.config/scc/exceptions.json 1.1 KB ✓ exists rw
Cache ~/.cache/scc/ 15.7 KB ✓ exists rw
────────────────────────────────────────────────────────────────────
Total 23.1 KB

Configure Claude Code status line integration.

Terminal window
scc statusline [OPTIONS]

Options:

OptionDescription
-i, --installInstall the SCC status line script
--uninstallRemove the status line configuration
-s, --showShow current status line config

Examples:

Terminal window
# Install status line
scc statusline --install
# Check current config
scc statusline --show
# Remove status line
scc statusline --uninstall

Check for CLI updates and refresh cached configurations.

Terminal window
scc update [OPTIONS]

Options:

OptionDescription
-f, --forceForce check even if recently checked

Examples:

Terminal window
# Check for updates
scc update
# Force refresh
scc update --force

What gets updated:

  • CLI version check
  • Organization config cache
  • Team config caches (for federated teams)
  • Plugin marketplace indexes