Druumen Cockpit

Editor groups + tabs cockpit for Claude Code workflows. A VS Code extension that gives you:

• Tabs Overview — a single panel listing every tab across every editor group, with tags, sticky notes, and an at-a-glance per-tab activity dot.
• Workspace Agenda — a collapsible BlockNote editor at the top of the panel for free-form notes that aren't tied to any one file.
• Claude Code Session Tracking (optional, Phase 3) — when paired with @druumen/sessions-db, Cockpit auto-registers every Claude Code session as you work, displays hub-spoke session graphs, and lets you attach a session to any tab.

Status

Phase 3 — Marketplace Pre-Release. Available on the VS Code Marketplace behind the Pre-Release toggle; the macOS surface is dogfooded and green, Windows and Linux smoke is in progress. Expect rough edges. The stable (even-minor) channel arrives at Phase 7 after the full cross-platform smoke matrix is green.

Install

From VS Code (Pre-Release):

1. Open the Extensions view (⇧⌘X / Ctrl+Shift+X)
2. Search Druumen Cockpit
3. Click the dropdown next to Install → Install Pre-Release Version

From the command line:

code --install-extension druumen.cockpit-vscode --pre-release

From source (contributors):

cd tools/cockpit-vscode/extension
npm ci
npm run package:inventory   # builds .vsix + verifies D15 supply-chain controls
code --install-extension cockpit-vscode-*.vsix

Privacy

• No telemetry. Cockpit never makes network calls beyond VS Code's extension marketplace updater.
• All data local. Tab tags, notes, workspace agenda, attached sessions live in VS Code's workspaceStorage. Session tracking data is stored in .dru-code/ (per-workspace) or tickets/_logs/ (for the Druumen monorepo); both are local-only by design.
• First prompt preview opt-out. Cockpit's Setup Wizard offers a storeFirstPrompt checkbox controlling whether sanitized prompts are saved to your local sessions store. Toggleable any time in VS Code Settings.

Licensed Apache 2.0. See the LICENSE and NOTICE files bundled in the extension for full terms and attribution.

Architecture

3 layers, each independently optional:

L0 works fine on its own; L1 layers in when you enable sessions tracking via the Setup Wizard; L2 is internal Druumen workflow only.

Reporting issues

This is internal-stage. File issues at the project's tracker (GitLab internal). Public marketplace tracker arrives at Phase 7.