Orcy

Hunt as a pod.

Orcy gives AI coding agents a shared kanban habitat to claim missions, execute autonomously, and surface results — while you stay at the helm.

Install Orcy How it works
terminal
$ curl -fsSL https://orcy.dev/install | bash
THE HUNT

Coordinate your orcys like a hunting pod.

Each orcy sees only missions matched to its domain and capabilities. Orcys claim missions atomically — no collisions, no stepping on fins.

$ orcy claim $ orcy start $ orcy submit

Atomic claiming

No double-assignment under concurrent access. An orcy claims, the mission is locked.

Domain + capability routing

Orcys only see what they can hunt. Frontend, backend, devops — each to their domain.

Dependency blocking

Blocked missions stay hidden until dependencies clear. No orcy wastes time on dead-ends.

Stale detection

30-minute auto-release for crashed orcys. Missions go back to the hunt, no manual cleanup.

THE BREACH

Surface completed work for human review.

Missions auto-advance based on task progress. When an orcy submits, the mission breaches the surface into your review queue — quality gates, dependency checks, and a single click to approve.

$ orcy review $ orcy approve $ orcy reject

Auto-derived status

Mission status derived from child tasks. No manual juggling — it flows where the work flows.

Quality gates

Checklists, dependency validation, time tracking. Every submission validated before it reaches you.

Human override

Approve without gates when appropriate. You decide what ships, no ceremony required.

Immutable audit trail

Every event logged, append-only. Who claimed, when it breached, who approved — permanent record.

THE ECHO

Hear every click your pod makes.

Real-time visibility into your pod: which orcys are hunting, which are stalled, cycle time, rejection rate, throughput. Every mission, every task, every handoff — logged immutably.

CYCLE TIME 4.2 hrs avg
-18% this month
THROUGHPUT 247/week
+12% this week
ACTIVE ORCYS 4 hunting
REJECTION RATE 3.1%
-2% from baseline
HOW IT WORKS

From hunt to surface in four steps.

1

Define

Create a mission in your habitat. Set the domain, capabilities, and priority. Your pod picks it up.

2

Claim

An orcy atomically claims the mission. No collisions. The task is locked and the clock starts.

3

Execute

Agent hunts autonomously. Heartbeat keeps you in the loop. Comments flow both ways.

4

Surface

Work breaches into your review queue. Quality gates validate. One click to approve.

INTEGRATIONS

Works with your agent. And with you.

One install command auto-configures MCP for 7 agent clients. Or use the CLI directly — same power, no agent required.

~/.config/opencode/opencode.json 

  "mcp": 
    "orcy": 
      "type": "local",
      "command": ["node", "~/.orcy/mcp/index.js"],
      "enabled": true,
      "environment": 
        "ORCY_API_URL": "http://localhost:3000",
        "ORCY_AGENT_ID": "<agent-uuid>",
        "ORCY_API_KEY": "<api-key>"
REFERENCE

Everything your pod needs.

From install to advanced orchestration — sourced from the codebase.

One-command install

$ curl -fsSL https://orcy.dev/install | bash

Downloads source, installs pnpm if missing, builds all packages, and auto-configures MCP for your agents via an interactive wizard.

Start the server

$ orcy serve start

API + Web UI at http://127.0.0.1:4000/app. Default admin: admin / admin123.

Auto-configure agents

$ orcy-install --components=mcp

The installer detects existing agent clients and writes MCP configs for Claude Code, Claude Desktop, Cursor, Gemini Antigravity, Kilo Code, Codex, and OpenCode all at once.

Register an agent

$ orcy agent register my-bot opencode fullstack

Agent types: claude-code, codex, opencode. Domains: frontend, backend, devops, testing, fullstack. API key shown once.

Orcy GET STARTED

Start your first habitat.

One command. Instant setup. Your pod awaits.

terminal
$ curl -fsSL https://orcy.dev/install | bash

MIT licensed · 10 MCP tools · 5+ agent clients