Provider Commands

scc provider show

Show the currently selected agent provider preference.

scc provider show

Output: Prints the current preference — ask, claude, or codex.

• ask — SCC prompts every time multiple providers are available
• claude — default to Claude Code
• codex — default to Codex

---

scc provider set

Set the global provider preference.

scc provider set <preference>

Arguments:

Argument	Description
preference	Provider to set: ask, claude, or codex

Examples:

Ask every time

scc provider set ask

When both providers are connected and you run scc start, SCC prompts you to choose.

Prefer Claude

scc provider set claude

SCC defaults to Claude Code without prompting.

Prefer Codex

scc provider set codex

SCC defaults to Codex without prompting.

---

Provider Resolution

When starting a session, SCC resolves the provider using this order:

1. --provider CLI flag — highest priority, overrides everything
2. Resume provider — when resuming a session, the original session’s provider is used
3. Global preference ask — if you set scc provider set ask, SCC prompts whenever multiple providers are viable
4. Workspace last-used context — SCC remembers which provider you used last in each workspace (stored in .scc/config.local.json, gitignored) and uses that context to preselect a sensible default or reuse the only viable provider
5. Global preference (claude or codex) — the value set by scc provider set
6. Single viable provider — if only one provider is allowed and ready, SCC uses it automatically

# Override for a single session
scc start --provider codex ~/project

# In non-interactive mode, --provider is required when multiple providers are available
scc start --non-interactive --provider claude ~/project

Note

In non-interactive mode (CI/CD), SCC errors if multiple providers are available but no --provider flag is given. Always specify --provider in automation scripts.

Tip

Teams can standardize on Claude, Codex, or both. The provider commands let developers switch quickly without changing the org or team governance model.

---

Provider Readiness

Each provider has independent readiness states:

State	Meaning
Launch-ready	Auth credentials and container image are both present
Auth cache present	Auth exists but image needs building (auto-built on first start)
Image available	Image exists but auth is missing or expired
Sign-in needed	Neither auth nor image — connect via scc setup

Check readiness with:

scc doctor                    # Check all providers
scc doctor --provider codex   # Check a specific provider

---

Connecting Providers

Providers are connected during scc setup:

scc setup

During setup, SCC offers to connect both Claude Code and Codex. Each provider authenticates via its own browser sign-in flow:

• Claude Code — Anthropic browser sign-in
• Codex — OpenAI browser sign-in (uses localhost:1455 for OAuth callback)

You can connect one or both. Connecting a second provider later is done by re-running scc setup.