Config Commands
scc config
Section titled “scc config”Manage SCC configuration.
scc config [ACTION] [KEY] [VALUE] [OPTIONS]Actions:
| Action | Description |
|---|---|
set KEY VALUE | Set a configuration value |
get KEY | Get a specific value |
show | Show all configuration |
edit | Open config in editor |
explain | Explain effective configuration with sources |
validate | Validate .scc.yaml for this workspace |
paths | Show file locations with sizes and permissions |
Options:
| Option | Description |
|---|---|
--show | Show current config |
--edit | Open config in editor |
--field FIELD | Filter explain output |
--workspace PATH | Workspace path for project context |
--team TEAM | Team profile to use for explain/validate |
--json | Output explain/validate as JSON envelope |
Examples:
# Show current configurationscc config show
# Explain where settings come fromscc config explain
# Explain specific fieldscc config explain --field plugins
# Validate project config in the current workspacescc config validate
# Validate with a specific teamscc config validate --team backend
# Edit configurationscc config editscc config explain
Section titled “scc config explain”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:
scc config explain --jsonJSON includes data.blocked_items and data.denied_additions for automation.
scc config validate
Section titled “scc config validate”Validates project config (.scc.yaml) against team/org policy gates and reports blocked or denied additions.
scc config validate --team backendscc config paths
Section titled “scc config paths”Show all SCC file locations with sizes and permissions.
scc config paths [OPTIONS]Options:
| Option | Description |
|---|---|
--json | Output as JSON |
--show-env | Include XDG environment variables |
Example output:
SCC File Locations────────────────────────────────────────────────────────────────────Config ~/.config/scc/config.json 2.1 KB ✓ exists rwSessions ~/.config/scc/sessions.json 4.2 KB ✓ exists rwExceptions ~/.config/scc/exceptions.json 1.1 KB ✓ exists rwCache ~/.cache/scc/ 15.7 KB ✓ exists rw────────────────────────────────────────────────────────────────────Total 23.1 KBscc statusline
Section titled “scc statusline”Configure Claude Code status line integration.
scc statusline [OPTIONS]Options:
| Option | Description |
|---|---|
-i, --install | Install the SCC status line script |
--uninstall | Remove the status line configuration |
-s, --show | Show current status line config |
Examples:
# Install status linescc statusline --install
# Check current configscc statusline --show
# Remove status linescc statusline --uninstallscc update
Section titled “scc update”Check for CLI updates and refresh cached configurations.
scc update [OPTIONS]Options:
| Option | Description |
|---|---|
-f, --force | Force check even if recently checked |
Examples:
# Check for updatesscc update
# Force refreshscc update --forceWhat gets updated:
- CLI version check
- Organization config cache
- Team config caches (for federated teams)
- Plugin marketplace indexes