Skip to content
AI4 min read

Rollcall: a menu bar app for keeping track of Claude Code sessions

Run a few Claude Code sessions at once and you lose track of what each one is for and which one is waiting on you. Rollcall is a small open source Mac app that fixes that.

Claude Code sessions are easy to start and easy to forget. One in the terminal, one in the desktop app, one in VS Code, each doing a different job for a different client. Nothing shows you all of them in one place. So I built a small Mac menu bar app that does. It's called Rollcall, it's free and open source, and this is what it does and how it works.

The problem

Running one session is fine. Running five is where it falls apart, for two reasons. The first is that you forget what each one is for. A terminal tab called `zsh` tells you nothing about the task you gave it forty minutes ago. The second is that a session can stop and wait for you without you noticing. Claude asks permission to run a command, you're looking at something else, and it sits there until you happen to click back. The work wasn't slow. It was parked. Both are the same problem underneath: the state of your sessions is spread across every window they run in.

What Rollcall does

  • Lists every Claude Code session running on your Mac: terminal, desktop app and IDE extensions.
  • Shows the project, what the session was asked to do, the ticket if there is one, and whether it's working, finished, idle or waiting for input.
  • Puts a count in the menu bar of the sessions waiting on you.
  • Sends one notification when a session needs you. Clicking it opens that chat in the Claude desktop app, or brings the terminal or editor forward.
  • Keeps a to-do list for the day, grouped by client, and shows which sessions are working on which task.

To-dos by client

The to-do list is the part I didn't plan and now wouldn't remove. You add a task with a client, and each task shows the status of the sessions working on it: waiting for input, working, finished or not started. A session links to a task on its own when the task title has the session's ticket number in it, something like `SHOP-214`. Otherwise you pick the task from the session's edit form. Open tasks carry over to the next day. That gives you the view a list of sessions can't: not just what's running, but what you said you'd do today that nothing is running for yet.

How it works

Claude Code has hooks, which are commands it runs on events like a prompt being submitted, a permission request, or a session ending. Rollcall installs one small hook for those events. Each time one fires, the hook appends a single line to a local file and exits. It takes about 35 milliseconds, prints nothing and can't fail the session. The menu bar app watches that file and folds the events into one record per session. A prompt means working. A permission request means waiting for input. A stop means finished. Thirty quiet minutes means idle. Because every surface runs the same user-level hooks, the terminal, the desktop app and the IDE extensions all show up without any extra setup. Nothing leaves your machine. There are no network calls, and the app is read-only: it can't start, stop or reply to a session.

Asking Claude about it

Rollcall also ships a local MCP server, so any Claude chat can read the same data. Register it once:

bash
claude mcp add --scope user rollcall -- node "$(pwd)/dist/src/mcp/server.js"

Then you can ask things like "what sessions do I have running and which need me?" or "which of today's tasks haven't I started?". It has three tools: `list_tasks`, `list_sessions` and `get_session`. It works with the menu bar app closed.

Try it

bash
git clone https://github.com/brideo/rollcall.git
cd rollcall
npm install
npm run hooks:install
npm start

`hooks:install` adds the hook entries to `~/.claude/settings.json` and leaves your existing hooks alone. `npm run hooks:uninstall` takes them out again and puts the file back as it was.

What it doesn't do

  • Cloud sessions on claude.ai/code. They leave nothing on your machine to read.
  • Sessions on other machines.
  • Token or cost reporting.
  • A signed, packaged app. It's an Electron app you run from the repo, Mac only.

It was built with Claude Code from a one-page scope, which seemed like the right way to build it. If you try it and something's missing, open an issue on the repo.

Claude CodeAIMCPOpen sourceProductivity
Work with me

Got a project like this?

Tell me what’s slow, broken or stuck. You’ll get a straight answer within one working day.

Keep reading · Next in the blogPHP2Shell: the ACSC's PHP alert, and how I patched our Docker imagesEngineering7 min read

More in AI

All posts →