rosary

rosary

Experimental software. APIs, schemas, and behaviors change without notice. Use at your own risk. Contributions welcome — expect rough edges.

⚠️ Dispatch surface is currently broken. Recent Claude Code harness changes regressed the claude -p subprocess invocation path used by rsry_dispatch and the reconciler's hub-to-spoke sync (see rosary-a53b91 + rosary-403a1a). The bead/task-tracking surface (CLI + MCP) is unaffected — see "Use rosary as a task tracker only" below if that's all you need. The architectural fix is a tmux-per-agent spawn substrate (rosary-75555d, pre-scoped into 6 children); contributions welcome.

Autonomous work orchestrator for AI agents across multiple code repos. Local-first, open source.

Rosary structures work as beads — small, trackable units stored in each repo via Dolt. A reconciliation loop scans for ready beads, dispatches AI agents (Claude, Gemini) to execute them in isolated workspaces, verifies the results, and syncs status to Linear for human review.

The human reviews 5-10 feature PRs a day. The agents handle the atoms.

How it works

graph LR
    A[Scan repos] --> B[Triage & prioritize]
    B --> C[Dispatch to agent]
    C --> D[Agent works in<br/>isolated workspace]
    D --> E{Verify}
    E -->|pass| F[Close bead]
    E -->|fail| G[Retry with backoff]
    E -->|deadletter| H[Flag for human]
    G --> C

Bead lifecycle

stateDiagram-v2
    [*] --> open
    open --> dispatched: agent assigned
    dispatched --> verifying: agent completes
    verifying --> done: checks pass
    verifying --> open: retry
    verifying --> blocked: deadlettered
    blocked --> open: human /resume

Issue tracking with beads

Work items live in each repo as beads — an AI-native issue tracker backed by Dolt (version-controlled SQL). Rosary reads and writes beads directly over MySQL, no CLI shelling.

Beads are organized into threads (ordered progressions of related work) and decades (ADR-level groupings) via the BDR harmony lattice.

# Beads are managed via rosary's MCP tools or CLI:
rsry bead create "Fix auth bug" --priority 1 --issue-type bug --files src/auth.rs
rsry bead list
rsry bead search "auth"
rsry bead close rsry-abc123          # requires a verifiable test command in the description
rsry bead close rsry-abc123 --force  # override (legacy / non-impl beads)

Capture beads from any provenance

# Transcript → BeadSpecs (Session provenance)
rsry capture --from-session sessions/2026-04-29.md --commit

# Source file → BeadSpecs (Code provenance, optionally scoped to a symbol)
rsry capture --from-code rosary src/bead.rs --symbol BeadSpec --commit

# Markdown ADR → beads + Rust stubs for design review
rsry decompose docs/adr/0009-feature.md --stub-output .

Getting started

task build    # requires Task (taskfile.dev)
task test

# Register repos to watch
rsry enable ~/code/my-app
rsry enable ~/code/my-lib

# See what's ready
rsry status

# Dry run — see what would be dispatched
rsry run --once --dry-run

# Real run — dispatch agents, verify, close
rsry run --once --concurrency 3

# Continuous loop
rsry run

Use task build / task test instead of raw cargo — the Taskfile sets PKG_CONFIG_PATH for the fuse-t dependency via ley-line.

Use rosary as a task tracker only

The dispatch + reconciler surface is currently broken (see banner above). The bead/task surface is fully functional today — rsry bead * CLI subcommands, the MCP server (rsry serve --transport stdio), and the Linear sync all work independently of the broken dispatch path.

If you just want issue tracking — backed by Dolt, queryable via MCP, optionally synced to Linear — you can use rosary today as a pure task tracker. Two install paths:

macOS (full install — codesigns binary + sets up an HTTP MCP launchd service):

task build
task install                                 # macOS-specific: codesigns + launchd; binary lands at ~/.local/bin/rsry

Linux / Windows / any platform (build + copy; skips the macOS-only codesign + launchd steps):

cargo build --release
mkdir -p ~/.local/bin && cp target/release/rsry ~/.local/bin/rsry   # or any directory on $PATH

Then on any platform:

# Register your repos for tracking (no dispatch loop will run)
rsry enable ~/code/my-app