the reconciliation loop

you file the intent.
machines do the work.

rosary is an autonomous work orchestrator. you describe what needs to happen — as beads, small enough for a machine to hold. agents pick them up, one by one, in isolated worktrees. they build. they test. they surface PRs. you review what survives.

begin → watch the loop
// THE RECONCILIATION LOOP

it runs while
you sleep

every cycle, rosary scans your repos for open beads. it picks the ripest ones, assigns an agent, gives it a clean worktree, and watches. if the work passes verification, the bead closes. if it fails, it retries. if it can't figure it out, it flags you. the loop never stops unless you tell it to.

01 SCAN find ripe beads
02 TRIAGE rank + assign
03 DISPATCH agent gets a worktree
04 VERIFY build, test, lint
05 CLOSE PR or deadletter
open waiting
dispatched in hands
verifying checking
done closed
// WHAT ARE BEADS

work items
for machines

a bead is a unit of work small enough for an agent to complete in one session. "fix auth bug." "add retry logic." "write the migration." beads live in your repo, backed by dolt — version-controlled SQL. they organize into threads (sequences) and decades (chapters). the rosary is the structure.

◊

multi-repo

register any repo. rosary watches them all. file-level overlap detection prevents two agents from touching the same code at once.

Δ

isolated worktrees

each agent gets its own git worktree. clean room. if the work fails, the worktree vanishes. your main branch never knows.

○

any model

claude, gemini, or your own agent definitions. rosary doesn't care what runs — it cares that the tests pass.

▹

verification

build, test, lint. every bead must pass before it surfaces. failures retry with backoff. three strikes and it deadletters to you.

the human reviews 5 PRs a day.
the agents handle the atoms.

that's the deal. you hold the intent. the machines hold the implementation. rosary is the thread between.

// PROTOCOL

speaks MCP
natively

20+ tools over streamable HTTP. connect claude code, connect your own agents, or hit the hosted endpoint. rosary doesn't have a UI — it has a protocol.

your agents connect here

bead CRUD. dispatch control. pipeline queries. workspace management. thread + decade organization. all as MCP tool calls, all over streamable HTTP + SSE.

mcp.rosary.bot live 
# self-hosted
rsry serve --transport http \
  --port 8383

# or the hosted endpoint
mcp.rosary.bot

# some of the tools:
rsry_bead_create
rsry_bead_search
rsry_dispatch
rsry_pipeline_query
rsry_status
...+15 more
// BEGIN

open source.
always.

register your repos. write some beads. let the loop take over.

view source → connect via MCP