Claude Source Control
Per-session source control panels for multiple Claude Code agents.
Running multiple Claude Code sessions at once? This extension gives each one its own Source Control panel — named Eclipse, Quasar, Nebula, etc. — showing only the files that agent modified. It also flags conflicts when two sessions touch the same file.
Quick Start
- Install from the VS Code Marketplace
- Open any git repo in VS Code
- Use Claude Code normally — active sessions appear in the Claude Sessions tree view in the Source Control sidebar. Click a session to show its SCM panel.
The extension auto-installs a lightweight hook the first time it activates. No configuration needed.
What You Get
- Claude Sessions tree view — lists all active sessions in the Source Control sidebar with file and conflict counts. Click to toggle SCM panels on/off.
- Per-session SCM panels — each Claude session gets its own panel, so you always know which agent changed what
- Conflict detection — files modified by 2+ sessions are flagged with a warning
- Stage, commit, discard — manage changes per-session, independently of the built-in Git panel
- Diff against HEAD — click any file to see what changed
- Terminal linking — each panel links to its Claude Code terminal (click to reveal)
- File decorations — modified/added/deleted/conflicted files are badged in the explorer
- Status bar — shows active session names and conflict count at a glance
Usage
From the Claude Sessions tree view (in the Source Control sidebar):
- Click a session to show its SCM panel (click again to hide it)
- Show All Panels button in the tree title bar to show all sessions at once
From a session's SCM panel:
- Click a file to diff it against HEAD
- Stage/unstage files with the +/- buttons
- Commit staged files per-session with a commit message
- Discard changes to revert individual files or entire sessions to HEAD
- Dismiss a session panel when you're done with it
How It Works
- On activation, the extension installs a PostToolUse hook into
.claude/settings.local.json. This hook runs after every Edit/Write/MultiEdit/NotebookEdit tool call and logs {session_id, file_path} to .claude/file-attribution.jsonl.
- The extension watches that file and intersects attribution data with
git status — only files that are both attributed to a session AND uncommitted appear in the panel.
- Each session gets its own SCM panel with Staged Changes, Changes, and Conflicts groups.
- Files touched by 2+ sessions are flagged as conflicts.
- When you commit or discard, stale entries are automatically cleaned up.
Settings
| Setting |
Default |
Description |
multiClaude.autoCreatePanels |
false |
Automatically create SCM panels when Claude sessions are detected. When disabled (default), sessions appear in the Claude Sessions tree view — click to show individual panels. |
To change a setting, open Settings (Cmd+, / Ctrl+,), search for "multiClaude", and toggle the option. Or add it directly to your settings.json:
"multiClaude.autoCreatePanels": true
Commands
| Command |
Description |
Multi-Claude: Install Attribution Hook |
Re-install the hook if it was removed or corrupted |
Multi-Claude: Refresh Panels |
Force-refresh all session panels |
Stage, unstage, commit, discard, and dismiss are available via inline buttons on the SCM panels.
Requirements
- VS Code 1.85+
node on PATH (the hook script uses it)- A git repository
Known Limitations
- Single-workspace only (uses the first workspace folder)
- No push/pull/sync — use the built-in Git panel for remote operations
Links
License
MIT
