Open source · BusyYaks

Your local agent agency,
run from a kanban board.

Claude Code sessions work your repos from one board per repo: they claim cards, ask you on them and hand over the PR with its CI and screenshots. Nothing merges before you approve.

  • Apache-2.0
  • Ruby 3.4 · Hanami 2.3
  • React 18
  • MCP
  • SQLite · PostgreSQL
  • self-hosted

busyyaks on GitHub 100 PRs a day

Screenshots v1.0.0-beta.2 · other projects shown as acme-N
BusyYaks' own board: the Needs you lane with a PR to review, the quiet finished workers, the launch bar with Launch, Worker, Sub team and Plain; the column counts; Backlog, To do, In progress and Local: Agent review with their cards, review rounds and owner sessions; the Agents sidebar lists the running sessions per project.
A board: the sessions that need you on top, the launch bar, the column counts, the cards with the session that owns each; the Agents sidebar on the right.
A card opened in Awaiting merge: its handoff box with the GitHub PR, the CI build, how to QA it and its screenshots drawn as blank plates; the Links rail with the local and public PRs and their state, the CI build, branches and commits; the owner session panel with its last ping.
A card in Awaiting merge: the handoff with the public PR, the CI build and how to check it; the Links rail with PRs, CI, branches and commits; the owner session.
The Today page: commit, own-commit, repo and merged-PR tiles with 7-day sparklines, a year-long commit heatmap, a 7-day table and the list of merged PRs; the agents sidebar on the right; the waiting widget counts to answer, to review and external.
Today: commits, repos and merged PRs with 7-day sparklines, a year of commits, the daily table and the merged PRs list.
The Today page on a phone: the stat tiles two per row, the commit heatmap and the waiting widget.
Today on a phone: the tiles two per row, the heatmap and the waiting widget.
The Workflow graph editor on a 15-column board, top to bottom: Backlog → To do → In progress → Agent review ↔ Author response loops, Local and Public Human review, Deploy check and Awaiting merge gates marked waits for you, Done and Cancelled; each arrow is a named transition; the column list with each column type on the right.
The workflow editor on a 15-column board: named transitions, review loops, the gates that wait for you.
How it works operator → board → lead → workers
One lead session per board, a worker session per card. Every session runs in tmux with a Claude Code Remote Control link.
  1. 1 Card You write a card on the repo’s board, or an agent creates one in Backlog.
  2. 2 Lead One lead session per board adopts the cards waiting for you and spawns a worker per card.
  3. 3 Claim The worker claims the card (kanban_claim) with its tmux session: comments and moves are typed into it.
  4. 4 Ask A question goes on the card (kanban_ask): it keeps its column, the options become buttons.
  5. 5 Hand over kanban_handoff carries QA steps, the PR, the CI build and, for a UI change, screenshots; it is refused while CI is unread or red.
  6. 6 Approve Only you move a card out of Human Check. The agent merges after that.
The workflow 7 columns · 6 column types
The template board (board.example.yml). Hand over is allowed from In progress or QA; a free Move edge keeps the board open. Columns, types and transitions live in the database; you edit them in a graph editor.
Backlogparked
nobody listens; agents may create cards here
To doqueued
waits for a session; a worker can be spawned per card
In progressworking
listened; the watchdog releases a card whose session is gone
QAreview
a further work column; review rounds are counted
Human Checkgate
agents enter only with kanban_handoff; only you approve
Ready to mergegate
approved; the agent merges the PR now, never before
Mergeddone
finished; owner and assignee kept as history
What runs docker compose + systemd --user
  • web container the dashboard SPA and the /api JSON API
  • mcp container the MCP endpoint: localhost only, bearer token
  • scanner container reads every repo under PROJECTS_ROOT, read-only
  • github container merged PRs, PR states, your network; the only holder of the token
  • notifier container types your comments and answers into the owning session
  • bin/launcher host starts tmux sessions, captures and answers their dialogs
  • bin/daily-report host · optional a local LLM writes the report; the server computes every number
Read the board
kanban_board · kanban_card · kanban_workflow · kanban_session_board
Own a card
kanban_register · kanban_claim · kanban_create · kanban_update · kanban_move
Talk to you
kanban_comment · kanban_ask · kanban_block · kanban_unblock
Hand over
kanban_pr_assign · kanban_attach · kanban_handoff
Panel
whats_new · list_projects · project · daily_facts · github_network · post_report
Quickstart full README →
git clone https://github.com/robertziel/busyyaks && cd busyyaks
bin/setup            # .env + config from the examples, secrets written
$EDITOR .env         # PROJECTS_ROOT, GITHUB_LOGIN, GITHUB_TOKEN, ...
bin/setup check      # every value compose needs, each problem with its fix
docker compose up -d --build --wait web mcp scanner github notifier

# connect Claude Code to the MCP server
vars=$(bin/env MCP_HOST MCP_HOST_PORT MCP_TOKEN) && eval "$vars"
claude mcp add --transport http --scope user busyyaks \
  "http://$MCP_HOST:$MCP_HOST_PORT/mcp" \
  --header "Authorization: Bearer $MCP_TOKEN"

# the host launcher (systemd --user; Ruby 3.2+, tmux, claude)
deploy/install-launcher.sh
Needs
  • Linux, Docker Engine 25+, compose 2.20+
  • git, a directory of git repos
  • a read-only GitHub token
  • host Ruby 3.2+ (stdlib only), tmux, the claude CLI
Not for
  • A team: one operator, no roles beyond operator and agent.
  • Not Linux, no tmux, no Claude Code.
  • Public, with no identity provider: auth none is for localhost.
  • Repos spread over many machines: the scanner reads one directory tree.
  • A public endpoint for agents: the MCP server is for local sessions only.
Repositories two repos that move together
Writing on BusyYaks 3 on this site