brizz-code

Run 10 Claude Code agents. Stay sane.

A terminal cockpit for orchestrating Claude Code sessions in parallel.
See which agents need you. Jump in, direct, jump out.

Sessions grouped by repo · Real-time status via hooks · PR state · One-key approve

Your agents are coding. brizz-code keeps you in control.

• 👀 See — real-time status across every repo
• ⚡ Act — jump, approve, repeat
• 🚀 Ship — PRs, branches, worktrees — all visible

Install

Homebrew (recommended)

brew install brizzai/tap/brizz-code

Shell script

curl -fsSL https://raw.githubusercontent.com/brizzai/brizz-code/master/install.sh | bash

Requires gh.

Go install

go install github.com/brizzai/brizz-code/cmd/brizz-code@latest

Requires Go 1.26+.

Requirements

• macOS
• tmux (brew install tmux)
• Claude Code

Quick Start

# Launch
brizz-code

# 'a' — new session in current repo
# 'n' — workspace picker with path autocomplete
# '?' — all keybindings

Features

Real-Time Status

Every agent's state, always visible. Hook-based detection — no polling, no delay.

● running   ◐ waiting   ● finished   ○ idle   ✕ error

Jump + Approve

Space jumps to the next session that needs attention. Y approves the prompt without attaching. Two keys, done. Cycle through a dozen waiting agents in seconds.

Git-Native Sessions

Sessions live under their repo. Branch name, dirty state, and full PR status on every header — CI pass/fail, review state, changes requested, unresolved threads. Collapse groups, filter with /, switch branches with b. Requires gh for PR info (optional).

Worktrees

w creates a new worktree with branch picker. Zero config — works with any repo. Each worktree gets its own isolated session. Custom workspace commands via .bc.json if you need them.

Fork Sessions

f forks a session — branches off the Claude conversation at that point. Try a different approach without losing the original. Both sessions keep running independently.

And more

• Session resume — restart with r, Claude picks up exactly where it left off
• Full terminal attach — Enter for full PTY, Tab for split mode (beta), Ctrl+Q to detach
• Auto-naming — sessions title themselves from your prompt
• 5 themes — tokyo-night, catppuccin-mocha, rose-pine, nord, gruvbox (S to switch)
• Chrome tab control — p opens PR in Chrome, reuses existing tab
• Bug reports — ! captures diagnostics and opens a pre-filled GitHub issue

Why brizz-code?

There are a dozen multi-agent session managers now. Most try to support every AI CLI under the sun. brizz-code takes the opposite approach: go deep on Claude Code, and nothing else.

Every feature is designed around how Claude Code actually works — hooks, conversation resume, session IDs, prompt structure. No generic "send keystrokes and hope" abstraction layer.

vs. the alternatives

	brizz-code	claude-squad	ccmanager	agent-deck
Status detection	✅ Hooks (real-time)	✅ Pane scraping	✅ Pane scraping	✅ Hooks
PR state (CI + reviews + threads)	✅	—	—	—
Smart session naming	✅	—	—	—
Fork conversation	✅	—	—	✅
Open PR in browser	✅	—	—	—
Session resume	✅	—	—	✅
Git worktrees	✅	✅	✅	✅
Multi-agent (Codex, Gemini…)	—	✅	✅	✅
Linux	—	✅	✅	✅
No tmux dependency	—	—	✅	—

The trade-off is intentional. Claude-squad and ccmanager support 5+ agents — but treat them all the same. brizz-code knows what Claude Code is. It reads hook status files. It resumes conversations. It knows your PR has 2 unresolved threads. It names sessions from your actual prompt. That depth is only possible by going narrow.

If you use Claude Code as your primary agent and want the tightest integration, this is it.

Keybindings

Key	Action
j / k	Navigate up/down
Enter	Attach to session
Ctrl+Q	Detach from session
Tab	Focus/unfocus preview (split mode, beta)
Space	Jump to next waiting/finished session
a	New session (current repo)
n	New session (workspace picker)
w	New worktree session
Y	Quick approve waiting prompt
f	Fork session
d	Delete session
r	Restart session
R	Rename session
b	Switch git branch
e	Open in editor
p	Open PR in browser
/	Filter sessions
S	Settings
!	Bug report / diagnostics
?	Help
q	Quit

Contributing

See CONTRIBUTING.md for development setup and guidelines.

License

Apache 2.0