orqa.sh

Run local agents as a working group.

Give this prompt to desktop Codex or cloud Codex to install Orqa, create a demo group, and see how agents can hand work to each other.

Give This To Codex

Manual Install

Install it yourself.

Shell Installer

curl -fsSL https://raw.githubusercontent.com/ianzepp/orqa/main/install.sh | sh

Homebrew

brew install ianzepp/tap/orqa

Cargo

cargo install orqa

Why Orqa Exists

Agents get more useful when they can coordinate.

Separate Identities

Run a planner, builder, reviewer, or researcher without forcing every agent through the same runtime home and global state.

Local Handoffs

Agents can send pod-local mail and tasks, leaving durable work items on disk instead of relying on a fragile chat transcript.

Wake Signals

Orqa can scan for unread mail and open tasks, then launch the agents that have work waiting.

Inspectable Runs

Run status, logs, and command records live under the agent home, so the coordination layer stays visible and debuggable.

What It Does

A local filesystem shape for agent groups.

Orqa does not try to be a cloud orchestration platform. It creates groups, agent homes, inboxes, task queues, config files, locks, and run records, then shells out to the backend you already use.

The project terms are simple: a group is a pod, and an agent identity inside that group is a fin.

ORQA_HOME/
  pods/
    demo/
      pod.toml
      fins/
        planner/
          fin.toml
          .codex/
          mail/
          tasks/
        builder/
          fin.toml
          .codex/
          mail/
          tasks/

First Group

Create two agents and send work between them.

Quick Start

orqa pod create demo
orqa fin create demo planner
orqa fin create demo builder

orqa mail send \
  --from planner@demo.orqa \
  --to builder@demo.orqa \
  --subject hello \
  "wake up"

orqa task send \
  --from planner@demo.orqa \
  --to builder@demo.orqa \
  --title first-task \
  "inspect the project and report back"

orqa plan demo
orqa loop --dry-run demo