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.
find ready beads
every cycle, rosary scans your registered repos for open beads. beads are units of work — small enough for a machine to complete in one session. "fix auth bug." "add retry logic." "write the migration."
multi-repo
register any repo. rosary watches them all. file-level overlap detection prevents two agents from touching the same code at once.
dolt-backed
beads live in your repo as version-controlled SQL. branch, diff, merge your work queue like code.
rank + assign
score by priority. check thread sequencing — same-thread beads wait their turn. filter blocked dependencies. respect per-repo concurrency limits. the highest-priority bead surfaces.
thread-aware
beads organize into threads (sequences) and decades (chapters). the rosary is the structure.
agent gets a worktree
an agent is assigned. it gets an isolated git worktree — clean room. the prompt is built from the bead description, file scopes, and the handoff chain from previous phases. the agent begins.
any model
claude, gemini, or your own agent definitions. rosary doesn't care what runs — it cares that the tests pass.
isolated
each agent gets its own worktree. if the work fails, the worktree vanishes. your main branch never knows.
build, test, lint
five verification tiers. commit exists? compile? tests pass? lint clean? diff sane (≤10 files, ≤500 lines)? first failure short-circuits. three strikes → deadletter to you.
you review
what survives
the human reviews 5 PRs a day. the agents handle the atoms. you hold the intent. the machines hold the implementation. rosary is the thread between.
the loop never stops unless you tell it to. ↑
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.
mcp.rosary.bot live# ── hosted (one command) ──
claude mcp add --transport http \
rosary https://rosary.bot
# ── local (self-hosted) ──
rsry serve --transport http
claude mcp add --transport http \
rosary http://localhost:8080/mcpopen source.
always.
register your repos. write some beads. let the loop take over.