Session Management

Sessions are the core unit of work in SCC. Each session is a Claude Code environment running in a Docker container, tied to a specific workspace.

Session Lifecycle

Starting Sessions

Smart Start (Recommended)

cd ~/project
scc

This auto-detects your workspace and shows Quick Resume if sessions exist.

Explicit Start

scc start ~/project

Start Options

Option	Description
`--resume`	Resume most recent session
`--select`	Interactive session picker
`--fresh`	Force new container
`--team TEAM`	Use specific team profile (session-only)
`--session NAME`	Name this session
`--dry-run`	Preview config without launching

Listing Sessions

scc sessions

By default, this shows sessions for your active team. Use --all to see sessions across teams, or --team <name> to filter explicitly.

 Sessions

  › feature-auth      draken · project-a · main · 2h ago
    bugfix-login      draken · project-a · fix/login · 1d ago
    main              draken · project-b · main · 5h ago

# Show sessions for all teams
scc sessions --all

# Show sessions for a specific team
scc sessions --team draken

Resuming Sessions

Resume Most Recent (Team-Scoped)

scc start --resume

Pick from List

scc start --select

Resume Specific Session

scc start --session feature-auth

Stopping Sessions

Stop Specific Container

scc stop <container-name>

Find the container name using scc list or docker ps.

Stop All SCC Containers

scc stop

This stops all running SCC containers at once.

Session Naming

Name your sessions for easier identification:

scc start --session "feature-payments" ~/project

When you have multiple features in progress, named sessions help:

Recent sessions:
  1. feature-payments (2h ago)
  2. bugfix-auth (1d ago)
  3. spike-new-api (3d ago)

Dashboard & Quick Resume

The dashboard appears when you run scc and shows a tabbed interface with Status, Containers, Sessions, and Worktrees:

 Status   Containers   Sessions   Worktrees

  › New session
    Resume last                draken · main · 2h ago
    Team: draken
    Containers: 2/3 running
    Settings

↑↓ navigate  ·  Enter open  ·  Tab switch tab  ·  n new  ·  q quit

Session Context

SCC tracks context for each session, including:

Last working directory
Active files
Session duration

Clear stale context:

scc context clear

Session Timeouts

Sessions can be configured to timeout after inactivity:

session:
  timeout_hours: 8
  auto_resume: true

Setting	Default	Description
`timeout_hours`	24	Hours before session expires
`auto_resume`	true	Advisory only in v1 (not enforced)

Container Cleanup

View Running Containers

scc list

# or
scc container

Prune Stopped Containers

scc prune

Prune with Dry Run

scc prune --dry-run

Shows what would be removed without actually removing.

Session History Cleanup

Over time, session history can accumulate. Use scc sessions prune to clean up:

# Preview what would be removed
scc sessions prune --dry-run

# Prune sessions older than 30 days (keeps 20 most recent per team)
scc sessions prune

# Keep only last 10 sessions per team
scc sessions prune --keep 10

# Prune sessions older than 7 days
scc sessions prune --older-than 7d

Troubleshooting Sessions

Session Won’t Resume

Cause: Container was pruned or crashed.

Solution: Start fresh:

scc start --fresh

Quick Resume Not Showing

Cause: Running from a different path than the original session, or viewing a different team.

Solution: Navigate to the exact workspace root and (if needed) show all teams:

cd ~/project  # Not ~/project/src
scc

# In Quick Resume, press 'a' to show all teams
# Or list sessions across teams
scc sessions --all

Session Stuck

Cause: Container in bad state.

Solution: Stop container and restart:

# Find the container name
scc list

# or
scc container

# Stop the specific container
scc stop <container-name>

# Start fresh
scc start --fresh