orch

orch is a shared to-do list for small, trusted teams, with automation on top.

Tasks are GitHub issues. A team member (or Claude Code, through MCP) adds them to a shared pool.
Each member runs tasks on their own machine, with their own Claude subscription. Nothing is pooled across accounts.
A task runs in a throwaway container that only sees its own git clone, then orch pushes a branch and opens a PR.
The central server only sees usage estimates and task statuses, never Claude credentials.
Everything runs in Docker: server, web, database, proxy, member agent, task sandboxes and all development workflows.

flowchart TB
    GH["GitHub App<br/>OAuth, webhooks, issues, PRs"]
    subgraph Server["Your server (Docker Compose)"]
        Caddy["Caddy<br/>HTTPS, web build, proxy"] --> API["server (Fastify)<br/>API, dispatcher, MCP, agent gateway"]
        API --> PG[("Postgres<br/>+ scheduled pg_dump")]
    end
    Browser["Browser"] -->|HTTPS| Caddy
    CC["Claude Code"] -->|"/mcp"| Caddy
    GH <-->|"REST, webhooks"| API
    subgraph Member["Member machine (any Docker host)"]
        Agent["agent container<br/>orch CLI, mirrors, clones"] --> Task["task container<br/>only the clone, non-root, claude"]
    end
    Agent -->|"outbound WebSocket /agent/ws"| Caddy

Members never open an inbound port: the agent connects out to the server over a WebSocket.

Get started

Using orch

Reference

Project