Docs

PaneCrew Docs

Reference material for running PaneCrew and understanding how it works. For the product pitch, see the homepage; for task-specific write-ups (running several agents at once, multiple terminal windows, ...), see the guides.

Interface tourA tour of the grid and the PaneCrew explorer, inside VS Code's own activity bar and editor groups.Install & runInstalling the PaneCrew extension from the Marketplace or a .vsix file.Focus-following explorerHow the file tree always tracks whichever pane has focus, and why that's PaneCrew's core mechanic.Commands & settingsEvery panecrew.* command and setting the extension contributes, and how to bind your own keys to them.

Quick start

  1. Install PaneCrew from the VS Code Marketplace— search "PaneCrew" in the Extensions view, or see the install guide for a .vsix build.
  2. Open the PaneCrew icon in the activity bar, then run PaneCrew: Open Project Grid…from the Command Palette and pick your first project folder.
  3. Run PaneCrew: Add Folder to Grid… for each additional project — every folder gets its own real, PTY-backed terminal, arranged automatically across a live grid.
  4. Switch between terminal panes as you work — the PaneCrew explorer follows whichever pane currently has focus, no manual re-navigation. See the focus-following explorer docs for why that's the extension's core mechanic.

PaneCrew is tool-agnostic: every pane is a normal shell, so it hosts Claude Code, Codex, Gemini CLI, GitHub Copilot CLI, OpenCode, or a plain shell equally well — nothing in the grid or the explorer is specific to any one CLI agent.