A menu-bar app that tells you what's waiting on you.
Your Claude Code and Codex sessions, your leads, what to film next, where the videos went, and how much disk is left. One glance, no asking.
Okay so, Tower is a little panel that drops out of the menu bar. Click the icon or hit Option+Command+T and it tells you, in one sentence, how many things are waiting on you, then lists them.
I built it because I run a lot of agents at once, and I kept asking the same questions over and over. "Where are we at?" "Where are the videos?" "What were the warm leads again?" "12GB??? it was 100gb free yesterday." Every one of those meant opening something, scrolling, or asking an agent to go look. Now I just open Tower.
It doesn't own any data. It reads the files that Claude Code, Codex and my other tools already write, and when it does change something, it goes through that tool's own command. So it's a view and a remote control, not another system to keep in sync.
The dithered hills at the top are the last 12 hours of your agents. Where they were working it piles up into hills. Where a finished agent sat waiting on you, it's cut out as a gap. The caption adds it up: how long they worked, and how long they waited on you.
It only counts waiting while you were actually at the Mac (within 20 minutes of a prompt you typed), so a session that finished while you were asleep doesn't count against you.
- Needs you, at the top. Any session whose turn ended and is waiting on you, follow-ups that are due today, and leads to check today. The menu-bar icon gets a dot while there's anything here.
- Agents. Every Claude Code and Codex session from the last 24 hours, with a live timer since your last prompt. Working, waiting, quiet for 10+ minutes, or idle. Click one to copy its session id and reveal the transcript.
- Fresh outputs. Videos, images and PDFs made in the last 72 hours across your folders, with thumbnails. Reveal in Finder, Quick Look (
Space), add to the Photos "Edited" album, or move to the Trash. Render frame dumps get folded into one row per folder, so 400 frames don't bury the one video you wanted. - Disk. Free space, a week of history, and a Reclaim view that finds Xcode build caches, Rust
target/folders and old videos, with sizes, so you can move them to the Trash in one go. - Leads, DM setter and film queue. These three read my own tools (more on that below). If the files aren't there, the cards just don't show up.
- Live, but quiet. It watches files with FSEvents and refreshes on midnight, on wake from sleep and when you open it. With the panel closed it does nothing at all.
| Leads and DMs | Film next and fresh outputs |
|---|---|
![]() |
![]() |
Everything in these screenshots is demo data from demo/seed.py, not my actual sessions or leads.
- macOS on Apple Silicon (built and tested on macOS 27, M1 Pro)
- Rust 1.85 or newer, to build it
There's no prebuilt app yet, so you build it from source:
git clone https://github.com/arhamhi/tower.git
cd tower
cargo build --release
./target/release/towerThe icon shows up in the menu bar. The first time you use Add to Photos, macOS asks if Tower can control Photos. That's the only permission it needs.
The headline font. The design uses Gambarino from Fontshare. Its licence doesn't allow putting the font file in a public repo, so it's not in here. Grab it free from Fontshare and drop Gambarino-Regular.otf into ~/Library/Fonts. Without it Tower falls back to Apple's New York, which looks good too.
Everything is optional. Put any of these in ~/Library/Application Support/Tower/config.json:
{
"ai_work": "/Users/you/Work",
"watch_roots": ["/Users/you/Work", "/Users/you/Downloads", "/Users/you/Movies"],
"node": "/opt/homebrew/bin/node",
"python": "/opt/homebrew/bin/python3",
"low_disk_gb": 15
}If the file is broken, Tower says so at the top of the panel and uses the defaults, instead of quietly ignoring you.
Three cards are wired to tools I built for myself. They're in here because this is the app I actually use. If you want them, feed them the same files:
- Reply checks read
Leads/outreach/tracker.json({"leads": [{"id", "company", "city", "state", "status", "next_date", "thread_url", "dm"}]}). A lead is due whenstatusissentandnext_dateis today or earlier. Mark replied or dead runsnode tracker.mjs mark <id> <status>next to it. - DM setter runs
python3 -B dm-setter/offer/tracker.py peekand reads the JSON it prints: daily caps, follow-ups due, and past replies. - Film next reads
cameraman/data/today-snapshot.json, which my content app writes: the film queue and how many posts went out this window.
All three paths sit under ai_work.
- No network. Tower never opens a connection, and there's no telemetry.
- Transcripts are read locally and never copied anywhere. Its cache keeps derived fields only (a short title, state, timestamps), never message content.
- It only writes to its own folders, plus three things you click: the lead tracker's own CLI, a Photos import, and Move to Trash.
- It never deletes anything for good and never empties the Trash. Every Trash move is confirmed, and paths are resolved and checked against your folders first, with symlinks and
..tricks refused. - Programs run with argument lists, never through a shell. The only links it opens are
httpsInstagram and Facebook threads. - Text from transcripts and leads is shown as plain text, length-capped, with control characters stripped.
~/.claude/projects/*.jsonl ─┐
~/.codex/sessions/**.jsonl ─┤ ┌─ one thread per source
tracker.json, peek, snapshot┼─► FSEvents + deadlines┤ reads, parses, publishes
media under watch roots ────┤ (midnight, wake, └─► shared snapshot
statfs ─────────────────────┘ 3 h idle, 72 h) │
▼
egui panel (repaints only while open)
│
actions: open, reveal, Quick Look,
Photos, Trash, tracker CLI
Agent state is read from the last meaningful record in each transcript (a typed prompt, a tool call, a turn ending), not from when the file last changed, because both tools keep writing bookkeeping after a turn ends. It's a heuristic over formats that aren't documented, so the panel says so when you hover.
The code is small on purpose: src/hub.rs runs the sources, src/sources/ has one file per thing it reads, src/actions.rs holds every side effect, and src/app.rs is the panel. The look is written down in DESIGN.md.
cargo fmt --check && cargo clippy --all-targets -- -D warnings && cargo testTo see it with fake data, build a demo home and point Tower at it:
python3 demo/seed.py /tmp/tower-demo
HOME=/tmp/tower-demo TOWER_OPEN_AT_LAUNCH=1 TOWER_PIN=1 ./target/release/towerTOWER_OPEN_AT_LAUNCH opens the panel on start, TOWER_PIN keeps it open when it loses focus, TOWER_SCROLL=600 opens it scrolled, and TOWER_DEBUG logs show and hide events.
Issues and PRs are welcome. This is my daily driver first, so the things most likely to get merged keep it fast, quiet and private. If you're not sure something fits, open an issue and ask.



