Private · experimental

One page over every session that builds the rest.

Desk, Torok and Canary are built by many Claude Code sessions at once. Tower puts them on one page: what asks you, what is in flight, what stalled. A pick on the page reaches the session that owns the work. A coordinator session keeps the page current and relays the pick.

Experimental. The first version ran for one day in September 2026; what the day showed is being folded into the next one. Personal work, on personal time.

How it is wired Where it stands

The Tower panel: program tabs, a one-line verdict, a Your move list with an ask, two decisions with recommended options and a move with its command, an In flight list of sessions, and a Tower task — The panel, rendered from synthetic sessions and decisions. Program tabs, then your move, then what is in flight.

What it does

Three things, in the order the day needs them.

Your move

Asks, decisions, moves

A session that needs a go, a decision with two options and a recommendation, a command to run before a deadline. One list, most urgent first. A keystroke picks.

In flight

Every session, grouped by program

Running, quiet or stalled, with its repo, branch and worktree. Rules in the database group sessions into program tabs; a fix on the page applies at once.

Relay

Picks reach the owner of the work

The coordinator relays a pick to the session that raised it, checks the revision it answers, and keeps a daily audit of delivered, read and acknowledged.

How it is wired

Three parts and one contract between them. The panel is a private page. Tower is a Claude Code session with a charter. Work sessions report in one line each. Facts pass through a scrubber before they are written; the database is the owner's alone.

Diagram of Tower: the owner and the panel page on the left, the Tower coordinator session with its refresh, scrub and relay steps in the middle, and three work sessions on the right; facts flow from the sessions through Tower into the panel, picks flow from the panel through Tower to the owning session — Facts flow left, picks flow right. Tower never pushes, deploys, merges, writes to the broker or answers a session's question for the owner.

Where it stands

Built in an evening. Contract, panel, scripts and charter landed on 2026-09-28. The gate is a page test against a fake runtime, script tests and a privacy scan.
Ran for a day. Program tabs, facts and the verdict line worked. The relay needed the owner's approval on the receiving side and messages expired unread; that is what the next version changes.
Off for now. Asks and decisions go back to each session's own chat until the delivery path is proven. The page and the scripts stay.
Synthetic on this page. Session titles, decisions and commands in the picture are fixtures. Real sessions carry names, paths and figures that stay private.

What it is not

Not a product. No download, no repository.
Not an agent that acts. Tower reads, writes a page and relays. Pushing, deploying and every decision stay with the owner.
Not part of Desk. The name was chosen so nobody confuses the two. Desk never sees Tower.

Contact

If you run several coding agents at once and want one page that tells you where you are needed, the contract is the interesting part. Get in touch.

Message on LinkedIn ↗GitHub ↗