Essential Commands

scc setup

Configure SCC’s org connection, connect Claude and/or Codex, and set your default startup behavior.

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:

Interactive

# Full interactive setup wizard
scc setup

Quick Setup

# Quick setup with org URL
scc setup --org https://example.org/scc-config.json --team backend

Standalone

# No organization config
scc setup --standalone

Tip

Private org config? Use --auth env:SCC_ORG_TOKEN (or GITHUB_TOKEN / GITLAB_TOKEN). SCC uses Authorization: Bearer by default and PRIVATE-TOKEN for GitLab URLs.

Note

scc setup is where most developers connect providers for the first time. You can connect Claude, Codex, or both, then choose whether SCC should ask every time or prefer one provider by default.

---

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:

Basic

# Initialize current directory
scc init

# Initialize specific project
scc init ~/projects/my-app

Force Overwrite

# Overwrite existing config
scc init --force

# Non-interactive overwrite
scc init --force --yes

Note

Creates a .scc.yaml file with sensible defaults including sections for additional_plugins, session settings, and optional additional_mcp_servers.

---

scc doctor

Run health checks to diagnose issues. Includes provider image and auth readiness checks.

scc doctor [WORKSPACE] [OPTIONS]

Arguments:

Argument	Description
WORKSPACE	Optional workspace path to check

Options:

Option	Description
-q, --quick	Quick status only
--provider PROVIDER	Check readiness for a specific provider (claude or codex)
--json	Output as JSON
--pretty	Pretty-print JSON output

Examples:

# Full health check (all providers)
scc doctor

# Check a specific provider
scc doctor --provider codex

# Quick status
scc doctor --quick

# Check specific workspace
scc doctor ~/projects/my-app

# JSON output for CI
scc doctor --json

Tip

Run scc doctor first when troubleshooting any issues. It checks the container runtime, Git, config, provider image availability, and auth readiness. If a provider image is missing, doctor shows the exact build command.

---

scc start

Launch an AI coding agent in a sandboxed container.

scc start [WORKSPACE] [OPTIONS]

Arguments:

Argument	Description
WORKSPACE	Path to workspace (auto-detected if omitted)

Options:

Option	Description
--provider PROVIDER	Agent provider override (claude or codex)
-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 (replace existing)
-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
--pretty	Pretty-print JSON (implies --json)
--non-interactive	Fail if input required
--allow-suspicious-workspace	Allow starting in suspicious directories (e.g., home, /tmp) in non-interactive mode

Examples:

Basic

# Smart start (auto-detect workspace)
scc

# Start in specific directory
scc start ~/projects/my-app

Resume

# Resume most recent session
scc start --resume

# Select from recent sessions
scc start --select

Team

# Use different team for this session
scc start --team security ~/project

Provider

# Start with a specific provider
scc start --provider codex ~/project

# Codex session with a specific team
scc start --provider codex --team backend ~/project

CI/CD

# Non-interactive for automation (--provider required when both are available)
scc start --non-interactive --provider claude --team backend ~/project

# Preview configuration
scc start --dry-run --json --provider codex

Note

If your organization allows both Claude and Codex, scc start follows your saved preference. When that preference is ask, SCC still prompts before launch and uses workspace context only to preselect a sensible default. If the chosen provider image or auth cache is missing, SCC auto-builds or starts the browser sign-in flow before launching.

Keyboard shortcuts in interactive mode:

Key	Action
Enter	Select/resume session
n	Start new session
Esc	Go back
q	Quit

---

scc stop

Stop running agent 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 picker
scc stop

# Stop specific container
scc stop scc-oci-b07ada0ef812

# Stop all sandboxes
scc stop --all

# Stop all without confirmation
scc stop --all --yes

---

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 status
scc status

# Detailed status
scc status --verbose

Note

scc status shows your current team, org config, active sessions, and any issues detected.