Agent orchestration and workspaces

marin-community/

loom

Single-binary session orchestrator that launches, supervises, and communicates with coding agents via REST, MCP, and a Vue dashboard.

What’s new here

Loom is a single daemon: one binary that owns a SQLite database, creates git worktrees, launches agents under supervised runtimes, and exposes every operation through a REST+SSE server. The MCP adapter, the CLI, and the Vue dashboard are all REST clients against that same server. Every operation is declared exactly once in a Rust source file; the REST route, JSON schema, MCP tool name, and CLI subcommand are all derived from that declaration, with no separate routing table to keep in sync.

What it does

Run loom server run and it starts a REST+SSE server on port 7878, a runtime supervisor, and a background monitor. From there you launch sessions with a goal string:

loom sessions launch "Add a /health endpoint"
loom sessions poll <session>
loom sessions wait <session>
loom sessions send <session> "try the curl again"
loom sessions archive <session>

Each session gets a weaver/<slug> branch and a worktree. Inside the worktree the agent uses a compact loop: loom summary, loom status set, loom channels read, loom artifacts write, loom channels send.

Loom tracks pull requests via the gh CLI, watches CI state, archives sessions on merge, and can trigger new sessions from a GitHub @loom mention in an issue, PR comment, or submitted PR review. Profiles are reusable launch templates that control agent selection, MCP access, environment posture, and opening instructions.

Who it’s for

Engineers who run Claude Code, Codex, or similar CLI agents regularly and want a persistent, auditable dispatch layer rather than ad-hoc terminal sessions. Also useful for small teams who want a shared server where multiple people can queue and review agent work through a browser without SSHing into the machine.

Try it

Requires Rust (cargo). From the repo root:

cargo build
mkdir -p ~/.local/bin
ln -sf "$PWD/target/debug/loom" ~/.local/bin/loom
loom setup
loom server run
loom open

Or via Docker Compose:

loom config render-env
cd deploy/standalone
docker compose up -d --build

How mature is it

Created January 2026, last pushed October 2026. 13 stars, 2 forks, 7 contributors, 10 open issues and pull requests. At least 100 commits in the last 90 days. No releases tagged yet. No license declared, so check with the authors before using it in production.