Panes

A fast, minimalist multi-pane cockpit for Claude Code on Windows + Git Bash, built on WezTerm.

Panes turns one keypress into a balanced grid of terminal panes — one per project — so you can run Claude Code across your whole workspace without manually opening, arranging, and hunting through windows. It's terminal-first and lightweight: panes are cheap shells, and Claude launches exactly where you want it.

▶ Watch the full video · Live site

What it does

• Centered launcher — pick a balanced grid (1 / 2 / 4 / 6 / 8 / 9), or press 0 to choose exact projects.
• Reshape any tab into N panes with Ctrl+1..9.
• Claude on demand — Ctrl+A then C (or auto-launch in every pane).
• Broadcast a line to every pane, zoom a pane, jump by number, fast in-place help.
• Minimal dark theme, project-named tabs, error-isolated settings.

Install

Windows (PowerShell):

git clone https://github.com/jiliangarette/claude-code-pane.git
cd claude-code-pane
powershell -ExecutionPolicy Bypass -File .\install.ps1

macOS / Linux (bash):

git clone https://github.com/jiliangarette/claude-code-pane.git
cd claude-code-pane
bash install.sh

On first launch Panes asks for your projects folder and saves it to ~/.config/ccp/roots.txt — no config editing needed. (Change it later with Ctrl+A then S, or edit ~/.config/wezterm/settings.lua.)

Requires WezTerm, bash (via Git for Windows on Windows; built-in on macOS/Linux), and Claude Code on your PATH.

Install with Claude Code (handoff)

Don't want to do it by hand? Paste this to Claude Code and let it set everything up:

Install Panes (https://github.com/jiliangarette/claude-code-pane) for me — a WezTerm-based multi-pane cockpit for Claude Code on Windows + Git Bash.

1. Make sure WezTerm is installed (winget install wez.wezterm, or the portable build from wezterm.org). Find wezterm-gui.exe and tell me its path.
2. Clone the repo into ~/projects and run install.ps1 with PowerShell (-ExecutionPolicy Bypass). It copies the config to ~/.config/wezterm, the scripts to ~/.config/ccp, generates the icon, and makes a Desktop shortcut. It will not overwrite an existing settings.lua.
3. Open ~/.config/wezterm/settings.lua and set projects and scan_roots to my real project folders, and auto_launch_claude to my preference.
4. Launch Panes from the Desktop shortcut and confirm the grid chooser appears. If WezTerm errors, read ~/.local/share/wezterm/wezterm-gui*log*.txt and fix it.

Keys

Key	Action
launcher 1-9 / 0	open N panes / pick projects
Ctrl+1..9	reshape tab into N panes
Ctrl+T · Ctrl+Tab · Ctrl+X	new tab · switch tab · close tab
Ctrl+Arrows · Alt+1..9	move · jump panes
Ctrl+A then C	launch Claude in pane
Ctrl+A then O / F	pick projects · pane-select (jump)
Ctrl+A then S / R / X	change projects folder · rename tab · close pane
Ctrl+Shift+B · Ctrl+Shift+Z	broadcast · zoom
Ctrl+H	help

Ctrl+Space is left free (e.g. for a Whisper hotkey).

Performance

WezTerm renders the grid on the GPU, so the panes themselves are cheap. The cost is Claude Code: each running instance is a Node process, and six or eight of them will saturate the CPU and RAM on a modest laptop — typing feels laggy because the machine is busy, not because the terminal is slow. This is workload, not Panes.

To keep things light:

• Leave auto_launch_claude = false (the default) and start Claude only in the panes you're actively using (Ctrl+A then C).
• Run fewer concurrent agents, or close panes you're done with (Ctrl+A then X).
• Set max_fps = 30 in settings.lua for a battery-first profile.
• Keep front_end = 'OpenGL' (the lowest-lag renderer on Windows).

License

MIT © Jilian Garette Abangan