Essential Commands
scc setup
Section titled “scc setup”Configure SCC with your organization settings.
scc setup [OPTIONS]Options:
| Option | Description |
|---|---|
-q, --quick | Quick setup with defaults |
--reset | Reset configuration to defaults |
--org SOURCE | Organization source (URL or github:org/repo) |
-t, --team TEAM | Team profile to select |
--auth SPEC | Auth specification (env:VAR or command:CMD) |
--standalone | Standalone mode without organization config |
--non-interactive | Fail fast instead of prompting |
Examples:
# Full interactive setup wizardscc setup# Quick setup with org URLscc setup --org https://example.org/scc-config.json --team backend# No organization configscc setup --standalonescc init
Section titled “scc init”Initialize a project with SCC configuration.
scc init [PATH] [OPTIONS]Arguments:
| Argument | Description |
|---|---|
PATH | Target directory (default: current directory) |
Options:
| Option | Description |
|---|---|
-f, --force | Overwrite existing .scc.yaml without prompting |
-y, --yes | Skip confirmation prompts |
--json | Output result as JSON |
--pretty | Pretty-print JSON output |
Examples:
# Initialize current directoryscc init
# Initialize specific projectscc init ~/projects/my-app# Overwrite existing configscc init --force
# Non-interactive overwritescc init --force --yesscc doctor
Section titled “scc doctor”Run health checks to diagnose issues.
scc doctor [WORKSPACE] [OPTIONS]Arguments:
| Argument | Description |
|---|---|
WORKSPACE | Optional workspace path to check |
Options:
| Option | Description |
|---|---|
-q, --quick | Quick status only |
--json | Output as JSON |
--pretty | Pretty-print JSON output |
Examples:
# Full health checkscc doctor
# Quick statusscc doctor --quick
# Check specific workspacescc doctor ~/projects/my-app
# JSON output for CIscc doctor --jsonscc start
Section titled “scc start”Launch Claude Code in a sandboxed Docker container.
scc start [WORKSPACE] [OPTIONS]Arguments:
| Argument | Description |
|---|---|
WORKSPACE | Path to workspace (auto-detected if omitted) |
Options:
| Option | Description |
|---|---|
-t, --team TEAM | Team profile for this session |
--session NAME | Session name for identification |
-r, --resume | Resume most recent session |
-s, --select | Interactive picker for sessions |
--fresh | Force new container |
-w, --worktree NAME | Create worktree before starting |
--install-deps | Install dependencies first |
--offline | Use cached config only |
--standalone | Run without organization config |
--dry-run | Preview configuration without launching |
--json | Output as JSON |
--non-interactive | Fail if input required |
Examples:
# Smart start (auto-detect workspace)scc
# Start in specific directoryscc start ~/projects/my-app# Resume most recent sessionscc start --resume
# Select from recent sessionsscc start --select# Use different team for this sessionscc start --team security ~/project# Non-interactive for automationscc start --non-interactive --team backend ~/project
# Preview configurationscc start --dry-run --jsonKeyboard shortcuts in interactive mode:
| Key | Action |
|---|---|
Enter | Select/resume session |
n | Start new session |
Esc | Go back |
q | Quit |
scc stop
Section titled “scc stop”Stop running Claude Code sandbox(es).
scc stop [CONTAINER] [OPTIONS]Arguments:
| Argument | Description |
|---|---|
CONTAINER | Container name or ID (picker if omitted) |
Options:
| Option | Description |
|---|---|
-a, --all | Stop all running sandboxes |
-i, --interactive | Multi-select picker |
-y, --yes | Skip confirmation |
Examples:
# Interactive pickerscc stop
# Stop specific containerscc stop claude-my-project-abc123
# Stop all sandboxesscc stop --all
# Stop all without confirmationscc stop --all --yesscc status
Section titled “scc status”Show current SCC configuration status.
scc status [OPTIONS]Options:
| Option | Description |
|---|---|
-v, --verbose | Show detailed information |
--json | Output as JSON envelope |
--pretty | Pretty-print JSON output |
Examples:
# Quick statusscc status
# Detailed statusscc status --verbose