Daily Workflow
This guide covers the most common SCC commands and patterns you’ll use day-to-day.
Starting Your Day
Section titled “Starting Your Day”Quick Resume
Section titled “Quick Resume”If you have a recent session for your current project:
cd ~/projectsccSCC opens the dashboard with your recent sessions:
Status Containers Sessions Worktrees
› New session Resume last draken · main · 1h ago Team: draken Containers: 2/3 running Settings
↑↓ navigate · Enter open · Tab/Shift+Tab switch tabs · n new · q quitForce a New Session
Section titled “Force a New Session”scc start --freshThis creates a new container even if you have existing sessions.
Resume Without Prompts
Section titled “Resume Without Prompts”scc start --resumeAutomatically resumes the most recent session for this workspace.
Working with Multiple Projects
Section titled “Working with Multiple Projects”Project A in the Morning
Section titled “Project A in the Morning”cd ~/project-ascc# Work on project A...# Press Ctrl+D or type 'exit' to leaveProject B in the Afternoon
Section titled “Project B in the Afternoon”cd ~/project-bscc# Different session, different containerPersonal Profiles (Optional)
Section titled “Personal Profiles (Optional)”If you customize plugins or MCP servers for a project, save them as a personal profile:
scc profile saveWhen 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 statusManaging Sessions
Section titled “Managing Sessions”List Recent Sessions
Section titled “List Recent Sessions”scc sessionsOutput (team-scoped by default):
Sessions
› feature-auth draken · project-a · main · 2h ago bugfix-login draken · project-a · fix/login · 1d ago main draken · project-b · main · 3h ago# Show all teamsscc sessions --allStop All Running Containers
Section titled “Stop All Running Containers”scc stopStop a Specific Session
Section titled “Stop a Specific Session”scc stop --session feature-authUsing Git Worktrees
Section titled “Using Git Worktrees”Create a Worktree for a New Feature
Section titled “Create a Worktree for a New Feature”-
Create the worktree
Terminal window scc worktree create ~/project feature-paymentsThis creates:
- Directory:
~/project/.worktrees/feature-payments - Branch:
scc/feature-payments
- Directory:
-
Enter the worktree
Terminal window scc worktree enter feature-paymentsThis 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
Section titled “List All Worktrees”scc worktree list -vOutput with status indicators:
Worktrees
› feature-payments scc/feature-payments +2 !1 ?3 bugfix-auth scc/bugfix-auth . main main ◆ (current)Status symbols:
+N— staged files!N— modified files?N— untracked files.— clean worktree◆— current worktree
Switch Between Worktrees
Section titled “Switch Between Worktrees”# Enter a different worktreescc worktree enter bugfix-auth
# Or use the interactive pickerscc worktree selectQuick Navigation Shortcuts
Section titled “Quick Navigation Shortcuts”scc worktree enter ^ # Enter main branch worktreescc worktree enter - # Enter previous worktree (like cd -)Team Switching
Section titled “Team Switching”Temporary Team Override
Section titled “Temporary Team Override”Sometimes you need to work as a different team for one session:
scc start --team security ~/projectThis uses the security team’s profile for this session only.
Permanent Team Switch
Section titled “Permanent Team Switch”scc team switch# Select new team interactivelyOr directly:
scc team switch frontendDebugging Configuration
Section titled “Debugging Configuration”See Effective Configuration
Section titled “See Effective Configuration”scc config explainThis 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
Section titled “Check Why Something is Blocked”scc config explain --field pluginsNon-Interactive Mode (CI/Scripts)
Section titled “Non-Interactive Mode (CI/Scripts)”For automation, use flags to avoid prompts:
# Will fail instead of promptingscc start --non-interactive ~/project
# Preview configuration as JSONscc start --dry-run --json
# Combine for CI pipelinesscc start --dry-run --json --non-interactive ~/projectDashboard Navigation
Section titled “Dashboard Navigation”The dashboard uses a tab-based interface with four sections:
| Tab | Description |
|---|---|
| Status | Quick actions, team info, container count |
| Containers | Running Docker containers with action menus |
| Sessions | Recent Claude sessions for resume |
| Worktrees | Git worktrees with status indicators |
Action Menus
Section titled “Action Menus”Press Enter on any resource to open its action menu:
| Resource | Available Actions |
|---|---|
| Container | Attach shell, View logs, Stop/Resume, Delete |
| Session | Resume session |
| Worktree | Start session in worktree |
Keyboard Shortcuts Reference
Section titled “Keyboard Shortcuts Reference”| Key | Action |
|---|---|
↑↓ | Navigate list |
Enter | Open action menu / Select |
Tab | Switch between tabs |
Space | Toggle details panel |
n | Start new session |
t | Switch team |
r | Refresh |
s | Open Settings & Maintenance |
? | Show help |
Esc | Close panel / Clear filter |
q | Quit |
Container-Specific Keys
Section titled “Container-Specific Keys”When on the Containers tab:
| Key | Action |
|---|---|
K | Stop container |
R | Resume container |
D | Delete container |
a | Open actions menu |
Common Issues
Section titled “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.