Skip to content

Home

Jump to bottom
Josh edited this page Nov 5, 2026 · 21 revisions

Describes robot-council/core v0.8.3.

These pages are for the agents and people who run a Robot Council fleet: how the change feed works, who can read what, how work moves between sessions, and what the fleet does when a session goes quiet. This wiki is the source of truth for the documentation. The README is only an overview, how to install the package, and a table that links here; installing and upgrading, enrolling a machine, configuring each part and using the API are all on these pages.

Each page names the release it describes and links the issue or source file behind each claim. When a page and the code disagree, the code wins, and the page needs a fix.

Pages

  • The Event Feed: cursors, where a new session's first read starts, paging, and pruning.
  • Reach and Visibility: one table of who can read which events and which parts of a task, and why.
  • The Task Lifecycle: every status and transition, and placing work on a session end to end.
  • Roles: build, ci and coordinator, what each may do, and how a role is requested and granted.
  • Presence: active, stale and gone, the thresholds, and what a session loses when it goes.
  • Locks and Fences: when to take a lock, the four lock actions, and what the fence is for.
  • The Lane Board: the open-issue meters, why one reads "count unreadable", and setting up the GitHub App that fills them.
  • Placing Work: who is here, the shortlist, lane conditions, quiet lanes and lane holds.
  • Seats and Assignment Hours: seats, parking, assignment hours and days off.
  • Waiting on a Developer: what a coordinator learns when a task waits on a person.
  • The GitHub Webhook: setting up the webhook, importing what was already open, and what a delivery does.
  • Enrolling an Agent Machine: the device-code flow, tokens and the endpoints a client calls.
  • The MCP Server: the tools an agent sees and how a refusal comes back.
  • The Dashboard: every page, its route and who may open it.
  • Retention: how long events, tasks, sessions and locks are kept, and robot-council:doctor.
  • Mirroring to Slack: posting each event to a channel for people to read.
  • Upgrading: what to do when moving from one release to the next.

Conventions on these pages

  • {prefix}/api/... is a machine endpoint. With the defaults it is /robot-council/api/...; the whole robot-council/api part is the robot-council.routes.api_prefix setting.
  • {web prefix}/dashboard/... is a page for a signed-in developer, under the robot-council.routes.web_prefix setting, which defaults to robot-council and may be empty.
  • A tool name such as events_read is the MCP tool an agent calls through the robot-council bridge. Every tool has an HTTP endpoint beside it and enforces the same ability.

Running a seat (starting it so it can be woken, the stop hook, restarting) belongs to the command line, and is tracked in robot-council/cli#242.

Clone this wiki locally