Start RedEye sessions, answer questions in the inbox, steer mid-flight, watch the Claude transcript live, and track cost per task — all from one local web dashboard. One project or twenty, same screen.
You stay in control. The dashboard is single-user, local-only, and writes to your projects' .redeye/ files only when you click something. No cloud, no auth, no telemetry.
Note
Control Tower is a personal project maintained in spare time. It works, but updates are infrequent. Feedback and contributions welcome.
| Mission Control per-project phase, health, questions, up-next, cost |
Tasks backlog with priority, status, and recent ships |
|
|
- Node 20 or newer
- Claude Code with the RedEye plugin installed
git clone https://github.com/Bitmia-ai/ControlTower.git
cd ControlTower
npm install
npm run build && npm startOpen http://localhost:3200.
Always run as production.
npm run devis for working on Control Tower itself — see Contributing.
The npm start script hardcodes --port 3200, so PORT=4000 npm start has no effect. Use the next start form directly:
npx next start --hostname 127.0.0.1 --port 4000- Add a project — point it at a git repo (Control Tower walks you through
redeye:initif needed) - Click Start — RedEye picks up the top task and works its triage → plan → build → review → deploy → verify → merge cycle
- Answer questions — when RedEye logs an inbox question, the bell badges. Click, answer, RedEye picks it up next iteration.
- Steer or add tasks — type a one-liner; RedEye expands it into a full backlog entry
- Read the live tab — tools, thoughts, and inter-round messages stream in real time
- See what shipped — History tab shows each session's task, phase flow, and cost
The dashboard never writes to .redeye/* on its own — only when you click something. Everything stays in plain markdown files; you can mix and match with the RedEye slash commands inside Claude Code.
WeatherCLI-Sample is a small TypeScript weather CLI built end-to-end by RedEye driven through Control Tower — every commit, every spec, every retry-loop is in the repo's .redeye/ history. Clone it, register it as a project here, and the dashboard will load all 44 shipped tasks, per-task costs, and the full session transcripts.
git clone https://github.com/Bitmia-ai/WeatherCLI-Sample.git ~/WeatherCLI-Sample
# Add it from the home page → "Add Project" → /Users/<you>/WeatherCLI-SampleUseful as a reference for what a clean RedEye-driven project looks like, and as a smoke-test that Control Tower correctly hydrates a freshly-cloned .redeye/ tree.
Control Tower binds to 127.0.0.1 and has no auth. To reach it from another device, tunnel into the box.
ssh -L 3200:127.0.0.1:3200 user@your-serverOpen http://localhost:3200 on the laptop.
Make Control Tower reachable on your tailnet at https://<machine>.<tailnet>.ts.net:
npm run build && npm start # in one shell
tailscale serve --bg --https=443 3200 # in anotherTailscale requires production mode. Dev mode does not work behind reverse proxies — see tailscale/tailscale#18827. If the home page hangs on "Loading projects…", you are on dev mode; switch to
npm run build && npm start.
Traffic only crosses your tailnet — no public exposure, no external auth surface.
- Local-only. Binds to
127.0.0.1. Tunnel in via Remote access instead of exposing the port. - No authentication. Anything on your machine that reaches port 3200 can control your sessions.
- Trust your projects. Control Tower spawns Claude Code as your user with
--dangerously-skip-permissions. Don't add projects you don't trust.
You can drive RedEye directly from Claude Code with /redeye:start. So why use this?
- Multiple projects, one screen. Watch all your sessions at once instead of
tail -facross terminals. - Live transcript. Read what the agent is doing without attaching to a Claude Code session.
- Cost per task. Snapshotted on
done, aggregated per project, forecasted from velocity. - Mobile-friendly PWA. Install on your phone, answer inbox questions from the couch.
If you only ever run one project from one terminal, the slash commands are fine. Control Tower starts to pay off the moment you have two.
- Single-user, no auth. No accounts, no roles, no shared installs. One person, one machine.
- macOS / Linux only. Tested there; Windows is unsupported.
- No remote pushes. Inherits RedEye's policy — commits land locally, you push.
- Always run as production.
npm run devexists, but reverse proxies (Tailscale, ngrok), service-worker caching, and self-dogfood deploys all expect the prod server. - State lives in files, not a database. A corrupted
.redeye/state.jsonwill surface as a broken card; fix the file.
Does it replace the RedEye slash commands? No — same files, complementary UI. Mix and match.
Can I run it for a team? Not as shipped. Single-user, no auth.
What if I close my laptop? Sessions stop. On restart, click Start; RedEye's crash recovery picks up from the last checkpoint.
Does it phone home? No telemetry, no analytics. Talks to Anthropic only through the Claude Code processes it spawns.
How does cost tracking work?
Parses cost_usd from ~/.claude/projects/*.jsonl. Per-session = sum within the active transcript. Per-task = snapshot at done. Total = sum across all transcripts for the project.
Can I use it without RedEye? No. For generic Claude Code orchestration, use something else.
Why does dev run on webpack instead of Turbopack?
Turbopack has no documented directory-exclude API and walks the entire project root, which makes RedEye's .worktrees/T-N/ clones balloon the in-memory module graph past 80 GB. Webpack honors watchOptions.ignored in next.config.ts to mask them out. Production next build still uses Turbopack.
Port 3200 already in use — lsof -ti:3200 | xargs kill -9, or run on another port: npx next start --hostname 127.0.0.1 --port 4000.
npm run build fails with module-not-found — npm install then retry.
Home page hangs on "Loading projects…" — you are on npm run dev behind a reverse proxy. Switch to npm run build && npm start. If you are already on prod, check the network tab — a 403 on GET /api/projects means the CSRF middleware rejected an Origin header mismatch.
Project page shows "Something went wrong" — stale .next/ chunks served during a self-dogfood DEPLOY. Run npm run build && npm start to recover.
RedEye loop won't start — verify which claude works and ~/redeye/plugin.json exists. Re-install RedEye with --plugin-dir ~/redeye if not.
- Control Tower Cloud — coordination-only SaaS so you can watch sessions, answer questions, and steer from anywhere without exposing your machine.
- Telegram integration — answer inbox questions and steer from your phone without a browser.
See ARCHITECTURE.md for code map, request flows, invariants, and a "where to look for what" cheat sheet.
See CONTRIBUTING.md. Open an issue first for anything larger than a typo. Security issues: see SECURITY.md.
If you are working on Control Tower itself, use npm run dev for hot-reload, then verify against npm run build && npm start before opening a PR — the prod server is the one users actually run.
MIT — Copyright (c) 2026 Bitmia-ai