Running another agent is easy. Remembering which terminal has a question, which one failed, and which machine it runs on takes more attention.
We build pitwall at Quantic Studios. It is a free desktop terminal for running several coding agents at once. The sidebar shows what each agent is doing, and a keyboard shortcut takes you to the one waiting on you.
Version 0.2 adds shared sessions across machines and a board that groups agents by what they need. The screenshots below use demo tasks. The current patch is 0.2.2.
One session, several machines
An agent running on a build box should not require a separate window just to check whether it needs an answer. A shared session holds local tabs and tabs on configured SSH hosts together.
The sidebar groups tabs by machine. Each host has its name and latency beside its tabs. Remote panes also have a host tag and a colored focus ring.
Add a host to pitwall’s config.toml with window = true. Use an SSH destination that already works with your own SSH configuration.
[[hosts]] name = "box" ssh = "me@box.example.com" window = true Install pitwall and its agent hooks on that host too. The agents run there, so their hooks must report to the daemon there. The remote setup guide covers installation, version compatibility and Linux session persistence.
From the sidebar, + lets you pick the machine. Hover a machine header for its own +. Ctrl+Shift+T opens a tab on the current tab’s machine. From a shell, use:
pitwall new --host box pitwall new --host box '~/evals' -- codex pitwall new --host box -d -- codex Quote ~/evals so your local shell does not expand it. The folder and the command belong to box, and Codex must be installed there.
In Settings → Appearance → Machines, choose dividers or collapsible sections. A folded section still counts the tabs that need you.
Shared sessions in a desktop window require Linux or macOS. Windows SSH lacks the connection sharing that pitwall uses for this feature. Windows can run local sessions.
A disconnected host stays visible
When a host disconnects, its tabs keep their last screen and dim. The sidebar reports that the host is offline and shows the reconnect countdown.
Typing into those remote panes is disabled. pitwall does not queue keystrokes for a later connection. Approval controls wait until the host returns. Local tabs and other reachable hosts continue working.
The board shows what needs an answer
Press Ctrl+Shift+M, or Cmd+Shift+M on macOS, to open the board. Its default columns are Needs you, Failed, Working, PR open, Done and Queued.
Approval cards show the command with Allow and Deny. Long commands and commands that guard rules deny take you to the terminal instead. Workers fold into their parent’s card unless they need your attention. A worker with an open pull request gets a card in PR open.
The Scope menu lets you view this session, all sessions, one group, ungrouped tabs or one host. This is useful when you want to check only the work running on a particular machine.
Read the state before opening the terminal
The sidebar distinguishes a question from an approval, a ready plan from completed work, and a failed turn from an agent that is still working. It also tracks an orchestrator watching its workers and a task with an open pull request.
Ctrl+Shift+U jumps to an agent that needs you. On macOS, use Cmd+U. The new Ctrl+Alt+U shortcut returns to the pane where you last sent a prompt, across tabs and sessions. Its macOS shortcut is Cmd+Option+U. Automatic messages do not count as your prompt.
Mouse controls and keyboard controls
pitwall has clickable controls and settings pages alongside terminal panes. You can start with the mouse, then use the command palette and rebindable shortcuts as you learn them. Pinned tabs, tab colors and themes help distinguish work without renaming every terminal.
Version 0.2 also asks for confirmation before you close a tab or pane whose agent is working or waiting mid-turn. The dialog names the agents. You can change that behavior in Appearance.
Usage-limit auto-resume schedules survive daemon restarts and saved shutdowns. An agent that stopped at its plan limit can receive continue after the reset. This does not mean every interrupted process survives a reboot.
Install and try one task
pitwall is MIT-licensed and needs no pitwall account. You still install and authenticate the coding agents you use. Claude Code, Codex, OpenCode, Gemini CLI, Cursor CLI, pi and Oh My Pi are supported.
brew install quanticstudios/tap/pitwall For an existing Homebrew installation, run brew upgrade quanticstudios/tap/pitwall. On Windows with Scoop:
scoop bucket add quanticstudios https://github.com/quanticstudios/scoop-bucket scoop install pitwall Open pitwall, start an agent in a project, and check what the sidebar reports when the agent asks a question or requests approval. Add a remote host when you have work that belongs on another machine.
We use pitwall daily on Linux. The macOS and Windows builds have had less use. If a state is wrong, a useful report includes the agent version, what the agent was doing, and what pitwall displayed. Remove private output before sharing a screenshot.
Repository and downloads: https://github.com/quanticstudios/pitwall
Remote setup: https://github.com/quanticstudios/pitwall/blob/main/docs/remote.md
Release notes: https://github.com/quanticstudios/pitwall/releases/tag/v0.2.0
Latest patch: https://github.com/quanticstudios/pitwall/releases/tag/v0.2.2
