Daily Workflow

This guide covers the most common SCC commands and patterns you’ll use day-to-day.

Starting Your Day

Quick Resume

If you have a recent session for your current project:

cd ~/project
scc

SCC shows Quick Resume and defaults to New session:

Quick Resume — Team: ai-teamet

  ➕ New session (ai-teamet)
  👥 Switch team
  ⚫ ai-teamet · project · main  2h ago

[Enter] Select  [n] New session  [a] All teams  [t] Teams  [q] Quit

Force a New Session

scc start --fresh

This creates a new container even if you have existing sessions.

Resume Without Prompts

scc start --resume

Automatically resumes the most recent session for this workspace.

Working with Multiple Projects

Project A in the Morning

cd ~/project-a
scc
# Work on project A...
# Press Ctrl+D or type 'exit' to leave

Project B in the Afternoon

cd ~/project-b
scc
# Different session, different container

Personal Profiles (Optional)

If you customize plugins or MCP servers for a project, save them as a personal profile:

scc profile save

When plugins are installed inside the container and only exist in sandbox settings, SCC detects them and offers to import them into .claude/settings.local.json before saving.

Check status and drift anytime:

scc profile status

Managing Sessions

List Recent Sessions

scc sessions

Output (team-scoped by default):

Session         Workspace              Last Used   Team
feature-auth    ~/project-a            2h ago      ai-teamet
bugfix-login    ~/project-a            1d ago      ai-teamet
main            ~/project-b            3h ago      ai-teamet

# Show all teams
scc sessions --all

Stop All Running Containers

scc stop

Stop a Specific Session

scc stop --session feature-auth

Using Git Worktrees

Create a Worktree for a New Feature

Create the worktree
Terminal window
```
scc worktree create ~/project feature-payments
```
This creates:
- Directory: ~/project/.worktrees/feature-payments
- Branch: scc/feature-payments
Enter the worktree
Terminal window
```
scc worktree enter feature-payments
```
This opens a subshell in the worktree directory.
Start SCC in the worktree
Terminal window
```
scc
```
Exit when done
Terminal window
```
exit  # Leave the worktree subshell
```

List All Worktrees

scc worktree list -v

Output with status indicators:

~/project/.worktrees/feature-payments [scc/feature-payments]
  +2 !1 ?3  (2 staged, 1 modified, 3 untracked)

~/project/.worktrees/bugfix-auth [scc/bugfix-auth]
  .  (clean)

Switch Between Worktrees

# Enter a different worktree
scc worktree enter bugfix-auth

# Or use the interactive picker
scc worktree select

scc worktree enter ^    # Enter main branch worktree
scc worktree enter -    # Enter previous worktree (like cd -)

Team Switching

Temporary Team Override

Sometimes you need to work as a different team for one session:

scc start --team security ~/project

This uses the security team’s profile for this session only.

Permanent Team Switch

scc team switch
# Select new team interactively

Or directly:

scc team switch frontend

Debugging Configuration

See Effective Configuration

scc config explain

This shows every setting and where it came from:

plugins:
  - scc-safety-net (from: team/backend)
  - code-linter (from: project/.scc.yaml)

network_policy: corp-proxy-only (from: org/defaults)

Check Why Something is Blocked

scc config explain --field plugins

Non-Interactive Mode (CI/Scripts)

For automation, use flags to avoid prompts:

# Will fail instead of prompting
scc start --non-interactive ~/project

# Preview configuration as JSON
scc start --dry-run --json

# Combine for CI pipelines
scc start --dry-run --json --non-interactive ~/project

Keyboard Shortcuts Reference

Key	Context	Action
`Enter`	Session picker	Select/resume
`n`	Session picker	New session
`Esc`	Any picker	Go back
`q`	Any picker	Quit
`t`	Workspace picker	Switch teams

Common Issues

Problem	Solution
”Session won’t resume”	Container may have been pruned; start fresh
”Quick Resume not showing”	Check workspace path and team filter; press `a` for all teams
”Team switch not taking effect”	Switches only affect new sessions

See Troubleshooting for more solutions.