██████╗ ██╗████████╗██╗ ██╗ █████╗ ██╗ ██╗
██╔══██╗██║╚══██╔══╝██║ ██║██╔══██╗██║ ██║
██████╔╝██║ ██║ ██║ █╗ ██║███████║██║ ██║
██╔═══╝ ██║ ██║ ██║███╗██║██╔══██║██║ ██║
██║ ██║ ██║ ╚███╔███╔╝██║ ██║███████╗███████╗
╚═╝ ╚═╝ ╚═╝ ╚══╝╚══╝ ╚═╝ ╚═╝╚══════╝╚══════╝
🏎 watch you flying
The pit wall for your AI coding agents: multi-agent, one glance, zero surprise.
How many coding agents can you run at the same time? One? Three? Nine? pitwall keeps many local agents visible on one screen — what they're doing, who needs you, and where to look next — so you spend less time switching terminals and more time flying through the work. When agents relate, pair them, broadcast to them, and compare approaches side-by-side.
- 🖥 Many agents, one cockpit — see every independent Claude/Codex session without juggling terminals
- 🎯 Attention-driven tiles — status-colored frames show who is running, done, or waiting on you
- 🔔 Needs-you detection + audio ping — pitwall calls you back from another tab when an agent stalls on approval
- ⇄ Pair badges — same repo, two agents? one keypress brings them side-by-side
- 📢 Broadcast input — type once, Enter, every selected agent gets the same prompt
- 🤝 Agent-agnostic — Claude Code and Codex both first-class, no lock-in, more coming
- 🔐 Your tokens, your machine — pitwall never sees API keys; agents run under your credentials
- ⌨️ Keyboard-first — focus, zoom, page-switch, toggle panes —
Alt+Sreveals the full cheatsheet - 🧱 Sticker wall — a drop-zone for ideas; global and per-project
- 🔩 Real CLI —
pitwall status/doctor/ls/backup— not just a browser app
Tile contents are boxed out in this shot to keep real work private.
On a fresh Mac, three commands:
npm i -g pnpm # if you don't have pnpm yet
git clone https://github.com/ujjeeq/pitwall.git
cd pitwall
./pitwall.sh # installs deps, builds UI, starts daemon on :7777
# open http://127.0.0.1:7777Needs Node ≥ 20, pnpm, and a C/C++ toolchain for node-pty
(macOS Xcode CLT or build-essential python3 on Linux). Windows: use WSL2.
You also need at least one agent CLI installed and logged in — Claude Code or Codex. pitwall orchestrates the ones you already use; it doesn't include or replace them.
Once pitwall.sh is on your PATH (symlink to ~/.local/bin or a shell
alias), you get a real CLI:
pitwall # start in prod mode (same as `start`)
pitwall dev # dev mode with HMR
pitwall status # box-drawing dashboard: daemon health + project counts
pitwall ls # table of every project and its status
pitwall doctor # diagnose toolchain / agents / runtime issues
pitwall logs -f # tail daemon log, or `pitwall logs ui` for vite
pitwall dashboard # open the browser UI
pitwall backup # tar up ~/.pitwall for migration
pitwall completion zsh # emit a shell completion script
pitwall help # full grouped listing- Local first, zero leak. Your code and tokens never leave your machine.
- Agent-agnostic. Adapter layer, not special-cased code per CLI.
- Human-in-the-loop, not human-replaced. Make decisions cheaper, don't make them for you.
pitwall runs entirely on your machine and is built to be unsurprising about it:
- Loopback only. The daemon binds
127.0.0.1:7777— nothing is exposed to your network or the internet. - Your credentials, never ours. pitwall spawns the
claude/codexCLIs you already installed; agents run under your logins. pitwall never reads, stores, or transmits API keys. - Passive observation. Telemetry (status, phase, tool calls) is read from the transcript files Claude Code already writes to disk — pitwall tails them, it does not inject into or scrape the live TUI.
- No phone-home. No analytics, no telemetry upload, no outbound network calls. Your code and prompts stay local.
It does run real PTYs (your shell) and reads ~/.claude.json to surface
/cost and /mcp info — so run it on machines you trust, as you would any
local dev tool.
./pitwall.sh dev # daemon on :7777 + vite dev server on :5173Stop / restart / logs / build / clean all subcommands — pitwall help has
the list. Repo layout: packages/shared (schemas), packages/daemon
(local service, PTY management, adapters), packages/ui (React + Vite).
watch you flying — a tip of the helmet to F1® The Movie — He's Flying (Apple TV). Running multiple AI agents in flow isn't unlike running a lap on the edge — when it works, you stop thinking about the controls, and the decisions just happen.
MIT