We're Quantic Studios, the team building pitwall, a free, MIT-licensed desktop terminal for coding agents. This guide gets two agents into visible tabs, sets up their status reporting, and shows how to send a follow-up without interrupting a turn.
The goal is specific: spot the agent waiting for you while another agent is still working. Start with a small repository you can inspect.
The image shows a sample workspace, not a live customer project.
With Homebrew on Linux or macOS:
brew install quanticstudios/tap/pitwall
pitwall --version
pitwall
Linux is where we use pitwall daily. macOS and Windows builds are newer beta builds with less hands-on testing. Windows installation and platform limitations are in the install guide.
Claude Code and Codex must already be installed and authenticated separately. pitwall doesn't include either agent or pay for its usage.
The first window lists the agents on your PATH and offers to install their reporting hooks. The command-line equivalent is:
pitwall hooks install
The installer backs up agent configuration and preserves existing hooks. In Codex, run /hooks once to trust the new hooks. Restart agent sessions that were already running. The hook documentation explains the files this changes.
Inside a pitwall terminal, change to your repository. Open two visible tabs:
pitwall new -n explain -- claude "Explain this repository's entry points. Do not edit files."
pitwall new -n tests -- codex "Explain how this repository runs its tests. Do not edit files."
Both tabs appear in the sidebar. Watch their states as they work and finish. If an agent asks for permission or input, inspect the request in its tab. Ctrl+Shift+U jumps to an agent that needs you; on macOS, use Cmd+U.
These first tasks request no edits, so you can check the workflow before running agents that modify the same repository. Use separate worktrees for independent editing tasks.
The current beta includes pitwall send. From another pane in the same session:
pitwall send tests -- "Which test should a new contributor read first? Do not edit files."
The message queues until the agent is ready at its prompt. It doesn't answer a permission request. Queued messages live in memory and disappear if the daemon restarts.
For an agent-to-agent discussion, the message header includes the sender and a reply address. The released command guide covers replies, waiting for results and the message limit.
Check that the hooks are installed with the binary you're running. Include your OS, pitwall version, agent CLI version, expected state and reproduction steps in a bug report. Remove private project details before sharing screenshots or logs.
See the sample workspaces and supported-agent table. The latest release checked for this guide is v0.1.0-beta.8.