Claude Code plugin

One cockpit for every Claude Code agent.

Five repos, a dozen agents, one of them stuck on a permission prompt in a terminal you can't find. Tower shows every session in one place: who needs you, what each one is doing and changing, and a box to steer it.

claude plugin marketplace add alaturqua/tower-mods && claude plugin install tower@tower

Then type /cockpit in any session. Requirements and setup

Try it · this is the real cockpit with sample data · approve a request, switch views, start a workstream, fold the panels Open full screen ↗

What the cockpit does

A local web page served from your own machine, over every Claude Code session on it. It reads what each session reports and acts through the session itself, so nothing leaves your computer.

Who needs you, first. Permission requests and questions as cards, oldest first, with the agent's reason, a diff for edits and a badge on risky commands. Allow, deny or answer with a click or A / D.
Steer any session. Send a prompt, or type / for the session's own slash commands, in a drop-up like Claude Code's.
Workstreams. Start an agent in a fresh git worktree on its own branch, watch each one, rename or remove it.
Changes and PRs. Lines changed per agent and file, the pull request with CI and reviews, and squash-merge when it's green.
Health. Agents that look stuck, loop on the same failing command, or fill their context are flagged, and the timeline shows who worked and who waited on you.
The whole fleet. Table, cards or timeline; one prompt to many agents; jump to a session's window or attach to a background one. System, light or dark, remembered.

Answer from the cockpit, not the terminal

When an agent the cockpit launched wants permission, the question comes to you, not to a terminal nobody is watching.

Agent in api

Bash git push origin main

Asks to run a command.
Held

Waiting for approval in the cockpit

Nothing runs. You get a notification and a card.
You, anywhere

AllowDeny

One click or keypress.
Runs once

✓ git push origin main

The agent retries; that exact call goes through, nothing else.

Launched from the cockpit

Permission prompts and questions come to the cockpit.

Started by hand

Keeps its own dialog. The cockpit shows what it waits on, and Jump brings its window forward.

Want every session?

Set remoteAnswers to always in /config.

Or stay in the terminal

The same plugin works inside Claude Code too, so you never need the browser.

/tower

Tower · 4 sessions · 1 needs you

▸! dbt-platform needs-input Bash: git push origin main 2m

~ web working Running tests 10s

✓ infra done Migrated 12 models. 5m

· api (bg) idle 1h

Needs approval: Bash git push origin main

[ Allow ] [ Deny ]

Send to dbt-platform…

1 needs you · tower-mods ⎇ main* · Opus 5.5 · high · auto · ctx 42% · $1.23

type /tower

The tower pane

Every session in a pane beside your conversation: who needs you on top, allow, deny, answer, send a prompt, jump, or launch a background agent.

in every session

Notifications

A desktop notification when a session needs you: a permission prompt, a question, a long turn finishing.

at the bottom

Status line

How many sessions wait on you, then folder, branch, model, effort, mode, context and cost.

Install

One line adds the marketplace and installs the plugin. Install it everywhere: every session then reports to the cockpit and can be steered from it.

claude plugin marketplace add alaturqua/tower-mods && claude plugin install tower@tower

On Windows, run the two commands one after the other, in PowerShell or Command Prompt. Neither takes both in one line: PowerShell 5 has no &&, and Command Prompt has no ;.

Open the cockpit: /cockpit in any session starts it and opens your browser. It listens on this machine only, behind a one-time link.
Needs: Node.js 18 or newer for the cockpit, and gh for pull requests. Sessions started before installing need a restart to report and receive.
Launching agents: Claude Code must have been trusted in a repository once (open Claude Code there and accept the prompt) before the cockpit can start agents in it.
Early access: Claude Code mods are new; the API can change between releases. See the changelog.

Help: update, restart, stop

The cockpit is a small server that keeps running after the session that started it. Updating the plugin doesn't touch it, so it needs one step to pick up a new version.

Update

Update the plugin, then reload it in every open session:

claude plugin marketplace update tower && claude plugin update tower

Then type /reload-plugins in your sessions and /cockpit in any of them. A cockpit of an older version is replaced by the new one on its own, and your open browser tab keeps working.

Restart or stop

In any session:

/cockpit restart
/cockpit stop

From a shell, with the plugin folder in place of the placeholder:

node "<plugin folder>/cockpit/server.mjs" --restart
node "<plugin folder>/cockpit/server.mjs" --stop

Stopping ends only the server. Your agents keep running and keep their status files; the cockpit finds them again when it starts.

When something is off

The page says forbidden: open it through /cockpit, which carries the link's token. The link is also in ~/.claude/tower/cockpit.json.
The port is taken: start it on another one with --port 4748, or set TOWER_COCKPIT_PORT.
A prompt stays "Queued": that session started before Tower was installed. Restart it or run /reload-plugins in it.
A launch fails: open Claude Code in that repository once and accept the trust prompt.
No pull requests show: install the GitHub CLI and run gh auth login.
The page looks old after an update: run /cockpit restart, then reload the tab.
Uninstall: /cockpit stop, then claude plugin uninstall tower.

Settings are in /config under the plugin, and the README lists each one. Still stuck? Open an issue with your version from claude plugin list.