Claude Squad
Multi-session tracking for Claude Squad worktrees.
Claude Squad Integration
Claude Squad runs multiple Claude Code instances in parallel, each in its own git worktree, managed through tmux sessions. Dashcam's Claude Squad bridge connects to these tmux sessions and tracks each worktree as a separate swim lane in the timeline.
Bridge Architecture
The Claude Squad bridge monitors active tmux sessions created by the cs CLI tool. It detects new sessions, associates them with their worktree paths and branch names, and routes their events to dedicated swim lanes.
tmux sessions (cs CLI)
├── session-1 (worktree: feature-auth, branch: feat/auth)
├── session-2 (worktree: feature-api, branch: feat/api)
└── session-3 (worktree: fix-tests, branch: fix/tests)
│
▼
Squad Bridge ──normalize──▶ SQLite + WebSocketEnable the bridge by starting Dashcam with the --squad flag:
dashcam start --squadMulti-Session Tracking
Each Claude Squad instance runs as an independent Claude Code session. The bridge correlates these sessions so that the Dashcam timeline shows them as parallel swim lanes under a single view:
┌─────────────────────────────────────────────────────────┐
│ 09:00 09:15 09:30 09:45 10:00 │
├─────────────────────────────────────────────────────────┤
│ feat/auth ──●──●──◆──●──●──●──●──◆──●── │
│ feat/api ────●──●──●──●──●──────────●──●── │
│ fix/tests ──────●──●──●──■──●──●──●── │
└─────────────────────────────────────────────────────────┘Each lane is labeled with the git branch name, making it immediately clear which task each agent is working on.
Worktree Awareness
The bridge detects the worktree path for each Claude Squad session. This means the Code panel in Dashcam shows diffs from the correct worktree — not from the main working directory. When you scrub the playhead over a feat/auth event, the Code panel shows changes in the feat/auth worktree, with the correct base branch for diffing.
Getting Started
- Start Claude Squad as usual with the
csCLI - Start Dashcam with the squad bridge enabled:
dashcam start --squad- Open
http://localhost:57580— active Claude Squad sessions appear automatically
The Claude Squad integration is a partial integration in the current version. Event capture relies on Claude Code hooks within each tmux session, and some Claude Squad lifecycle events (session pause/resume, worktree cleanup) may not be fully tracked. Full integration is planned for a future release.
Current Limitations
- Pause/resume tracking — When Claude Squad pauses and resumes a session, the gap may not be accurately reflected in the timeline
- Session naming — Sessions are identified by their tmux session name and branch; custom labels from Claude Squad are not yet imported
- Worktree cleanup — When Claude Squad removes a worktree, the corresponding swim lane data is preserved but the lane is not automatically archived
- Cost aggregation — Token costs are tracked per-session but not yet rolled up into a Claude Squad-level aggregate view