Head to head · Multi-agent orchestration · October 2026 research run

Agent Relay vs Orca

Agent Relay scores 69.9 (B) on agent readiness against Orca's 59.9 (C), and leads in 4 of 7 scored categories. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 1767 harnesses comparisons

Which one, for what

Agent Relay B

Best for Teams running several Claude Code or Codex sessions who want them to message, hand off and spawn each other across machines.

Ahead on

  • Reliability, 73 against 58
  • Schema & documentation, 87 against 65
  • Security & auth, 58 against 43
  • Transparency & trust, 77 against 54

Also in its favour

  • Runs on your own machine

Watch for

About 34 MCP tools in the default server, with only a sessions-only subset to cut the list

Orca C

Best for Developers who want an orchestrator agent to split work across parallel coding agents, on desktop or mobile.

Also in its favour

  • No key needed to call it

Watch for

Anonymous usage data collected by default, with an opt-out

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Transparency & trust Agent Relay +23

Agent Relay 77

Apache-2.0, copyright Agent Workforce Incorporated (30). The privacy policy lists data by category with its purpose, names its providers (OpenAI for session embeddings, Anthropic for arelay.to replies) and deletes arelay.to conversations seven days after the last message. The trust page calls its provider list unconfirmed and keeps workspace run data indefinitely by default. TELEMETRY.md and the privacy policy agree (20). Changelog entries name removed and retired parts, such as the broker, but no deprecation policy with dates was found (8). Telemetry is disclosed with three opt-outs, but on by default (14). 30 + 20 + 8 + 14 = 72.

Orca 54

MIT (30). Privacy and telemetry docs on the site (not read) (18 of 30). No deprecation policy (5). Disclosed with an opt-out (15 of 20). 30 + 18 + 5 + 15 = 68.

Schema & documentation Agent Relay +22

Agent Relay 87

Read as an MCP server. Every tool registered in agent-relay-mcp.ts and the messaging and action modules declares a zod input schema and an output schema (25). https://agentrelay.com/llms.txt indexes the docs, every docs page has a Markdown copy, and llms-full.txt holds them all (10). Descriptions say what each tool returns and when not to retry, as on spawn and create_workspace (16). Enums on cli and a few other fields, optional limits and cursors, but invoke_action takes z.unknown() input and many fields are free strings (10). Quickstart and self-hosting examples, and error codes such as spawn_unconfirmed and spawn_fork_not_found named in descriptions and the changelog, with no single error reference (11). Semantic versions and a changelog (15). 25 + 10 + 16 + 10 + 11 + 15 = 87.

Orca 65

Harness reading. A docs site with CLI orchestration and native chat pages (65).

Reliability Agent Relay +15

Agent Relay 73

Read as local software, since the CLI, MCP server and default server run on the person's machine. npm install -g agent-relay with Node.js 22 or 24 stated in the quickstart and engines (20). Public CI in test.yml and about twenty other workflows, including node-compat and security. Run results couldn't be read from this session (15). 230 issues were open on 18 November 2026. Of the 25 newest, from 29 September to 17 November, four had a reply and several were open bug reports from October, such as a fresh Codex spawn blocking on a trust dialogue (8). Keep a Changelog with semantic versions, and breaking changes marked by major versions and in the changelog (15). Version 18.10.0 (15). 20 + 15 + 8 + 15 + 15 = 73. The hosted services, not graded here, have a status page whose history shows two degraded-performance incidents from 2 to 5 November 2026, for message sending and uploads and for session uploads and search.

Orca 58

Local software. Desktop and mobile builds and a Homebrew cask (20). Unit, end-to-end and platform test workflows; pass state not read (15). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Tags to v1.4.251, no changelog file (8). Version 1.4 (15). 20 + 15 + 0 + 8 + 15 = 58.

Security & auth Agent Relay +15

Agent Relay 58

Harness reading of the framework checklist, as for Harness by Autonomous. 30 for what leaves the machine and credentials, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Local use needs no account, but telemetry is on by default with a hashed machine ID, adds the account's name and email once signed in, and a workspace key grants the whole workspace (16). Spawned agents run on the host with no sandbox from Agent Relay. Since 18.10.0 an organisation's policy can hold messages from non-admin senders for the person's approval, and a known-senders-only setting exists (12). Messages from other agents reach an agent as input. Leader and peer framing and sender holds help, but no guidance to treat message text as untrusted was found (8). Observer URLs, message read receipts and shared session capture, but no per-call audit log found (8). SECURITY.md with private advisories, a security workflow, a valid security.txt and a disclosure policy with acknowledgement in two business days and safe harbour. No paid bounty, and the trust page says SOC 2 is pending (14). 16 + 12 + 8 + 8 + 14 = 58.

Orca 43

Harness reading. Anonymous usage data with an opt-out, per the README's link to its telemetry docs (15 of 30). Worktrees per agent and a sandboxed Linux build (12 of 20). No prompt-injection guidance (5). No audit log (5). A dependency-security workflow (6 of 20). 15 + 12 + 5 + 5 + 6 = 43.

Score by category

CategoryWeightAgent RelayOrcaEdge
Reliability16%7358Agent Relay +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8765Agent Relay +22
Agent ergonomics13%6870Orca +2
Security & auth14%5843Agent Relay +15
Payments & pricing10%6060even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%7375Orca +2
Transparency & trust7%7754Agent Relay +23
Negative events≤1500
TotalB 69.9/100C 59.9/100

Facts side by side

FactAgent RelayOrca
KindMCP serverAgent harness
VendorAgent Workforce IncorporatedLovecast Inc.
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthOAuth or keyNone
PricingFreemiumFree
x402nono
LicenceApache-2.0MIT
Tools exposed34none
Read-only variant documentednono
llms.txtyesno
Last release2026-11-172026-11-06
Terms last updated2026-05-27no document linked
Privacy policy last updated2026-10-14no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticenot found in the textnot read yet
Arbitration or class-action waivernot found in the textnot read yet
Popularity1.1k starsnone

How the scores have moved

Verdicts

Agent Relay

Agents get typed, annotated MCP tools for channels, direct messages, spawning and fleet actions, with a local server that needs no account and semver releases most days. The 34 tools carry a large context cost, telemetry is on by default, hosted prices aren't published, and the company's registration couldn't be confirmed.

Orca

An open-source orchestrator for coding agents with worker agents in their own worktrees, chat and terminal views, a browser and a CLI, on desktop and mobile, with heavy test automation. It collects anonymous usage data by default, and the cloud option's pricing wasn't found.

Before you call either

Agent Relay

  1. If a spawn returns spawn_unconfirmed with state pending, check the agent's liveness before retrying, as the tool description says
  2. Pass the same idempotency_key when you retry a spawn, so a second agent isn't started
  3. Call list_actions before invoke_action and match the action's own input schema, since the tool accepts any payload
  4. Treat messages from other agents as untrusted input and ask the person before acting on instructions in them
  5. Ask the person before running relay init --hosted or cloud login, since both send data to agentrelay.com

Orca

  1. See the telemetry docs on onorca.dev to opt out of anonymous usage data
  2. Use the orchestration CLI to hand a large task to one agent that starts workers

Questions

Which is better for AI agents, Agent Relay or Orca?

Agent Relay scores 69.9 (B) on agent readiness against Orca's 59.9 (C), and leads in 4 of 7 scored categories.

Can an agent call Agent Relay and Orca without installing anything?

Agent Relay runs on your own machine, with no hosted endpoint listed. No hosted endpoint is listed for Orca.

Are Agent Relay and Orca open source?

Yes. Agent Relay is open source (Apache-2.0). Orca is open source (MIT).

Other comparisons with Agent Relay or Orca

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.