Skip to content

CLI Overview

Complete command reference for SCC (Sandboxed Claude CLI).

These options are available on all commands:

OptionDescription
--debugShow detailed error information
--version, -vShow version and exit
--help, -hShow help for any command

All SCC commands use consistent exit codes:

CodeConstantMeaning
0EXIT_SUCCESSOperation completed successfully
1EXIT_ERRORGeneral/unexpected error
2EXIT_USAGEInvalid usage/arguments
3EXIT_CONFIGConfiguration or network error
4EXIT_TOOLExternal tool failed (git, docker)
5EXIT_PREREQPrerequisites not met
6EXIT_GOVERNANCEBlocked by governance policy
130EXIT_CANCELLEDUser cancelled (Esc/Ctrl+C)
Terminal window
scc start --dry-run --non-interactive --team ci .
exit_code=$?
case $exit_code in
0) echo "Config valid" ;;
3) echo "Config error" ;;
5) echo "Missing prerequisites" ;;
6) echo "Blocked by governance" ;;
*) echo "Other error: $exit_code" ;;
esac

Commands with --json support output a standardized envelope:

{
"apiVersion": "scc.cli/v1",
"kind": "CommandName",
"metadata": {
"generatedAt": "2025-12-23T10:00:00Z",
"cliVersion": "1.5.0"
},
"status": {
"ok": true,
"errors": [],
"warnings": []
},
"data": { }
}
Terminal window
# Pretty print
scc status --json --pretty
# Parse with jq
scc start --dry-run --json | jq '.data.plugins'
# Check status in scripts
if scc org validate config.json --json | jq -e '.status.ok'; then
echo "Config is valid"
fi
CategoryCommandsPurpose
Essentialsetup, doctor, start, stop, statusCore workflow
Sessionssessions, contextSession management
Worktreeworktree *Parallel development
Teamteam *Team profiles
Profileprofile *Personal project profiles
Configconfig, statusline, updateConfiguration
Governanceexceptions, unblock, auditSecurity & policies
Organizationorg *Org admin commands
Terminal window
# General help
scc --help
# Command-specific help
scc start --help
scc worktree create --help
# Debug mode for troubleshooting
scc --debug start ~/project