Busy Bee — Development skill for Claude Code

busy-bee

A macOS menu bar app that gives a single glanceable view across all active Claude Code side projects: what got done recently, what's next, what's blocked, and what the agent is waiting on you to answer. Clicking a project opens a terminal and resumes that project's Claude Code session directly. You can also jot down a project that doesn't exist yet, queue tasks against it, and hand those tasks to Claude the moment you create its folder.

See [`docs/prd.md`](./docs/prd.md) for the full spec this was built from.

Requirements

• macOS. Non-negotiable: menu bar status item, AppKit dialogs, and osascript-driven Terminal control. The installer refuses to run anywhere else.
• Python 3.10+, and it must be the python3 the installer finds first. Machines with Anaconda or Xcode's python3 ahead on PATH often have 3.8/3.9 there -- check with python3 --version and pass PYTHON= if it's too old (see step 1).
• Claude Code, since everything on the dashboard is logged by agents running in it.
• Terminal.app (default) or iTerm for click-to-resume.

No Homebrew packages, no Xcode, no code signing -- `pip` pulls `rumps` and `pywebview` (and PyObjC underneath) into a local venv.

Quick start

Fine to run start-to-finish by an agent; every step is non-interactive and idempotent.

git clone https://github.com/nandita7krishnan/busy-bee.git ~/busy-bee   # keep the clone somewhere permanent
cd ~/busy-bee
./scripts/install.sh                 # venv, PATH symlinks, Claude Code hooks, LaunchAgent

Then verify:

dashctl --help                       # prints usage -> dashctl is on PATH
pgrep -f 'busy-bee' >/dev/null && echo running   # the menu bar app is up

You should see a 🐝 in the menu bar within a few seconds. From then on, every Claude Code session on the machine logs to it automatically -- no per-project setup.

Installation, step by step

The same install as above, one