Tower

A Claude Code plugin: one cockpit for every Claude Code agent on your machine, across all your repos. See who needs you, approve and answer, send prompts and slash commands, start agents in their own git worktrees, and watch what each one changes.

Try the live demo (in your browser, on sample data) · Site · Changelog

Install

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

On Windows, run the two commands one after the other. PowerShell 5 has no &&, and Command Prompt has no ;:

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

Install it everywhere: every session then reports to the cockpit and can be steered from it. Sessions that were already running pick it up after a restart or /reload-plugins.

Then type /cockpit in any session. It starts the cockpit in the background and opens your browser.

After an update, /cockpit swaps a cockpit of an older version for the new one by itself. /cockpit restart replaces it on demand and /cockpit stop stops it; from a shell, node plugins/tower/cockpit/server.mjs --restart or --stop.

Needs Node.js 18 or newer for the cockpit, and the GitHub CLI (gh) for pull requests. Mods draw nothing in the VS Code chat panel; for /tower and the status line, run Claude Code in a terminal (VS Code's integrated terminal works) or the desktop app's Code tab.

The cockpit

Area	What it does
Usage	The header shows your 5-hour and weekly rate limits (how full, when they reset) beside what all sessions have spent.
Needs you	Permission requests and questions as cards, oldest first: the agent's reason, a diff for edits, a badge on risky commands (pushes, deletes, deploys). Allow, deny or answer with a click, or A / D / 1–4. Always allow on a plain, low-risk command allows it and writes that exact command as a rule to the folder's .claude/settings.local.json, so it stops asking.
Fleet	Every session as a table, cards or a timeline (your choice is remembered): state, what it's doing, lines changed, PR and CI, context fill, cost, and how many subagents it has running. Stuck, looping, context-full and over-budget agents are flagged, and so are two worktrees changing the same file. Click any row, card or timeline lane to open that agent. Each row's ⋯ holds Continue, Compact, Rename, Open in editor, Jump to terminal, and below a divider Clear conversation and Stop; what a session can't do stays listed, greyed, with the reason.
Done	A log of finished runs, newest first: what each one said last, what it changed, how long it took and what it cost, and its PR. Click one to see its whole last message and its files; one whose session still runs opens that agent. Clear log empties it. Kept in ~/.claude/tower/history.jsonl.
Dashboard	Runs, spend and average run time over the last 14 days, and how long you kept agents waiting in the last hour. Charts of spend per day and per repository, the most expensive runs (click one to see what it did), and the fullest context windows.
Repositories and workstreams	The left rail groups sessions by repo and git worktree. + Add repository opens your system's folder picker (or type a path). + New workstream starts a background agent in a fresh worktree on its own branch (claude --bg -w). Pick 2–4 agents to give the same task to several worktrees and compare them side by side; Keep this one stops the others, removes their worktrees (their branches stay) and asks the kept one for a PR. The ⋯ menus rename or remove repos and worktrees.
Merge queue	When a repo has two or more green PRs, squash-merges them oldest first, checking each again just before its merge and stopping at the first that is no longer green.

Select several agents to send them all the same prompt, or stop them. Everything follows System, Light or Dark.

여기까지가 README 앞부분입니다. 나머지는 원문에서 읽을 수 있습니다. README 전문 보기 ↗