Tower

A macOS menu bar app with one panel for your coding tools: Claude Code, Codex and Cursor. It shows what you have used, what is left and when it resets. Your agent reads the same numbers over MCP, and Tower runs only on your Mac.

The screenshot uses invented accounts (scripts/demo-store.py).

Quick start

macOS 14 or later, Apple silicon:

gh release download --repo yonatangross/tower --pattern 'Tower.app.zip*'
shasum -a 256 -c Tower.app.zip.sha256 && ditto -x -k Tower.app.zip ~/Applications
mkdir -p ~/.local/bin && ln -sf ~/Applications/Tower.app/Contents/MacOS/Tower ~/.local/bin/tower
open ~/Applications/Tower.app

Then sign into each Claude Code account once with /login. For Cursor, click Connect Cursor on its row once; Tower keeps its own Cursor sign-in and never touches the Cursor app's. Blocked on first launch? See troubleshooting.

Install with your agent

Paste this into Claude Code, Codex or Cursor. The agent runs the steps in AGENTS.md without asking you anything, and stops if a check fails:

Install Tower from github.com/yonatangross/tower: follow AGENTS.md, section
"Install Tower for the user". Verify the checksum, link ~/.local/bin/tower,
register the MCP server for this agent, run `tower mcp --self-test`, and tell me
what you did. Do not open System Settings for me; tell me if macOS blocks the
first launch.

The agent downloads the release with gh, checks its SHA-256, installs to ~/Applications, links ~/.local/bin/tower, registers the MCP server and runs its self-test. If macOS blocks the first launch, it stops and asks you to press Open Anyway (First launch); it never changes Gatekeeper itself.

Register the MCP server by hand, if you prefer:

Agent	How
Claude Code	claude mcp add --scope user tower -- ~/.local/bin/tower mcp
Codex	~/.codex/config.toml: [mcp_servers.tower], command = "/Users/<you>/.local/bin/tower", args = ["mcp"]
Cursor	~/.cursor/mcp.json: {"mcpServers": {"tower": {"command": "/Users/<you>/.local/bin/tower", "args": ["mcp"]}}}

Then tower mcp --self-test (a non zero exit means the server is broken).

Playbooks

Playbook	For
Setup	install, first run, Keychain trust, adding accounts
Multi-account	several Claude Code seats, Codex, Cursor
MCP	let Claude Code, Codex or Cursor read your usage
Troubleshooting	Gatekeeper, Intel Macs, build errors, odd rows
Uninstall	remove the app and everything it stored

What it does

• Seats. Real Claude Code usage for each account you have signed into: usage per window, what is left, and the next reset. Codex and Cursor plans sit beside them.
• Comparison. Which of your seats has the most left.
• MCP server. tower mcp answers the same questions over the Model Context Protocol, so any agent (Claude Code, Codex, Cursor and others) can read the same numbers. See docs/mcp-surface.md.
• Extras. OpenRouter balance, agent lanes (Muse, Devin, the Cursor CLI, Antigravity, and Pi with its spend this month and today as a share of the OpenRouter budget) and live Claude Code sessions, when those tools are present.
• CLI. tower status, tower rotate, tower retrust, tower panelshot, tower selftest.

It reads the same numbers Claude Code's /usage screen shows, through an undocumented endpoint that can change with any Claude Code release.

Before you use it

• Tower reads the Claude Code credential from your login Keychain. With Remember Claude seats on (the default) it keeps each signed-in seat's access token in its own Keychain item, so it can read that seat's usage after you switch away, until the token expires. It never stores a refresh token and never renews a token; a seat whose token expired reads "needs login" until you sign into it again. Turn the option off, or press Forget, to delete those items.
• Check that using several subscriptions this way fits your provider's terms. Tower does not decide that for you.
• Nothing leaves your Mac except requests to the providers' own APIs.

Install

Requirements: macOS 14 or later on Apple silicon. The release zip is an arm64 build; on an Intel Mac, build from source.

From a release (no build tools needed):

gh release download --repo yonatangross/tower --pattern 'Tower.app.zip*'
shasum -a 256 -c Tower.app.zip.sha256
ditto -x -k Tower.app.zip ~/Applications

First launch: "Open Anyway"

Tower is not notarized by Apple (release builds are ad hoc signed), so when the zip came through a browser, macOS blocks the first launch with "Apple could not verify Tower is free of malware". This happens once per install. Check the checksum first (the shasum line above prints OK), then:

1. Open Tower once (double-click ~/Applications/Tower.app) and press Done on the warning.
2. Open System Settings, then Privacy & Security.
3. Scroll down to Security. Next to "Tower was blocked to protect your Mac", press Open Anyway.
4. Press Open Anyway again in the dialog and enter your login password if macOS asks.

Tower then starts normally and macOS does not ask again for this copy. The Terminal alternative is in troubleshooting. To remove Tower, follow uninstall.

This is the beginning of the README. Read the rest at the original. Read the full README ↗