Busy CrewA mod for BUSY Bar

For Claude Code & Codex · macOS

Your agents,
on your desk.

Busy Crew puts every Claude Code and Codex session on the LED strip of your BUSY Bar. Look up to see who’s working, who needs you, and who’s done.

Get it on GitHubInstall in a minute
Claude: 1 working, 2 done, 1 idle. Codex: 2 working, 1 done.

Read the strip

Readable from across the room.

Each session is a small character in its family’s color. The mark above it tells you where it stands, and whoever needs you always goes first.

  • Working

    In its family’s color: terracotta for Claude, blue for Codex.

  • Waiting for you

    A question or a permission. It brings the sessions view back on its own.

  • Done

    Stays green until you press the scroll wheel or the session moves on.

  • Idle

    Open but quiet. zzz when every Claude session is asleep.

  • Failed

    A failed turn, an unknown state, or a source it can’t read.

  • More

    Six slots on the strip. The rest fold into +N.

Hands on the bar

The knobs work too.

Cycle through views and clear finished results without touching your keyboard. Answering a question or granting a permission stays in Claude or Codex, on purpose.

Start / Pause
Cycle the views: sessions, tokens today, tokens this month.
Wheel · turn
One view forward or back.
Wheel · press
Acknowledge the ✓ on screen.
Back
Return to the sessions.
Off · Settings
Move the selector there to pause the display.
>_ Same from the terminal
uv run busy-crew view tokens   # or: sessions, month
uv run busy-crew ack           # acknowledge the ✓
uv run busy-crew refresh       # recount tokens now
uv run busy-crew status        # what's running, and why

Privacy

Everything stays on your Mac.

Busy Crew talks to one device: your BUSY Bar. No telemetry, no cloud service, no update check, no account. Nothing from your conversations is stored, logged or sent.

  • ~/.claude/sessions

    Claude Code

    Session IDs, busy or idle, timestamps. Transcripts are never opened. The optional hooks keep IDs and a keyed fingerprint per tool call, never your prompts or tool inputs.

  • read-only

    Codex

    Conversation and turn IDs from its databases, then the end of the last turn’s journal. Only turn events, approvals and questions are parsed: messages, reasoning and tool outputs stay undecoded.

  • ccusage · optional

    Tokens

    Today’s and this month’s totals per family, from ccusage, a third-party tool that reads your usage logs itself.

  • your network

    The bar

    A 72 × 16 frame and the bar’s button events. Over plain HTTP your network can see them, so use a trusted one.

What it keeps fits in one private folder: IDs, states, token totals and backups of your Claude settings.What is read, kept and sent

Install

Up and running in a minute.

  • A Mac and a BUSY Bar on the same network
  • Python 3.11+ and uv
  • Claude Code and/or the Codex app on this Mac
  • Optional: ccusage 20+ for the token views
git clone https://github.com/cmdai-hq/busy-crew.gitcd busy-crewuv sync --lockeduv run busy-crew install --address http://busybar.local --timezone Europe/Paris

Use your bar’s address. install adds a LaunchAgent and, after a backup, Claude Code hooks. uninstall removes both. Your agents show up within a few seconds.

Read the full guide