beekeeper

Run the guide session — walk the person through the decisions the sessions on the machine wait on, one at a time with the status quo and the why, relay each answer word for word to the session that asked, take their new ideas and input to the right place, and keep the roadmap board current. Always a session of its own, never the supervisor's. Use when the person asks for a guide, wants to go through their open decisions, or when a relayed `beekeeper guide handover --prompt` arrives.

Register a freshly started, empty Claude session with the running supervisor, then take the one task it hands over and work it to the finish. Use when the person starts an empty session ("Agent one", "Agent four") and types /register-agent, optionally with the session's name.

Run the desk's supervisor session — watch the other Claude sessions and the machine's memory, swap, load and labs for hours at a time (typically overnight), keep every session's work finishing, schedule new work from the roadmap board, prevent the desktop-wide OOM, and coordinate sessions that turn out to be working on the same repo, issue, PR or environment. Use when the person asks for a supervisor, a babysitter for the running sessions, an overnight watch, or when a session titled "supervisor" starts or a relayed `beekeeper handover --prompt` arrives.

The rules a worker on a beekeeper desk follows from its first tool call to its report — registration, leases, merges, the GitHub budget, the machine, secrets and questions for the person. Load it at the start of every task a supervisor hands out, whether the session was started with `beekeeper agents start` or registered with /register-agent.