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

Harness vs Traycer

Harness scores 60.9 (C) on agent readiness against Traycer's 57 (C), and leads in 5 of 7 scored categories. Traycer leads on reliability. Both do multi-agent orchestration.

Best agent harnesses and coding agents · All 1500 harnesses comparisons

Which one, for what

Harness C

Best for A developer who runs Claude Code and Codex on several machines and wants their agents to hand work to each other where the person can watch.

Ahead on

  • Schema & documentation, 85 against 65
  • Agent ergonomics, 77 against 65
  • Security & auth, 54 against 42
  • Payments & pricing, 40 against 30

Also in its favour

  • Runs on your own machine
  • Free to start without a card

Watch for

Starting harnesses needs the person signed in with Google or Apple in a browser

Traycer C

Best for Teams who want several coding agents working together with shared context and boards.

Ahead on

  • Reliability, 65 against 40

Also in its favour

  • No key needed to call it

Watch for

Privacy Mode is opt-in for individuals; with it off, prompts may be logged

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.

Reliability Traycer +25

Harness 40

Read as local software, since the agents run on the owner's machines. A one-line installer from Autonomous's CDN, DMG and AppImage builds, and App Store and Google Play apps, with macOS and Linux stated as supported and Node managed by the installer, per the 17 October check, not re-read on 4 November, since Autonomous's terms forbid access to its sites by automated means, including scripts or web crawlers, and its hosts are paused pending the founder. Not on a package registry we could read (20). A public CI workflow plans a run per changed component, with Linux unit tests, the desktop suite in four shards, repository tooling tests, typechecks and a bundle test, and a separate CLI end-to-end workflow. We could not read run results, so 15, the value this run gives public CI that runs the tests with an unreadable result (10 on 17 October, corrected). Open issues could not be read, because github.com answers our proxy with 403. Unchecked, so scored absent (0). Tags follow semver per component, but there is no changelog for the app or CLI and breaking changes are not marked in the repository (5). The CLI went from 0.4.x to 0.5.x on 29 October (v0.5.1_cli); a 0.x minor is exempt from the breaking-change term under this run's provisional reading. The CLI agents call is 0.5.33 (3 November 2026), the npm MCP package is 0.2.0, and Agents can start other agents is still an experiment, so the agent surface is pre-1.0 (0). 20 + 15 + 0 + 5 + 0 = 40. Accounts and the relay are hosted by Autonomous with no status page found on 17 October.

Traycer 65

Local software. Builds for macOS, Linux and Windows, and package-manager publishing workflows (20). test.yml, CodeQL, OpenSSF Scorecard and secret scanning run on the repository; 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). CHANGELOG.md (15). Host 1.5.3 (15). 20 + 15 + 0 + 15 + 15 = 65.

Schema & documentation Harness +20

Harness 85

Read as an MCP server and CLI. Eleven tools in source at v0.5.33, each with a typed JSON Schema input built by one helper, required fields marked, plus --json on every command. No OpenAPI, which a stdio server does not need (23). llms.txt and a Markdown-like agents page written for agents, per the 17 October check, not re-read on 4 November, since Autonomous's terms forbid access to its sites by automated means, including scripts or web crawlers, and its hosts are paused pending the founder (10). The tool descriptions and server instructions say when to call whoami first, to prefer a new project over an existing folder, to read before telling a harness more, and that turning a setting on is the person's yes to give (20). An enum on agent and on the setting name, minItems on wait names, minimum and maximum on timeout_seconds, a minimum on chars and limit. machine, folder, project and model are free strings (12). Worked examples, the exit code table and the Next: line per the 17 October reading of the agents page and llms.txt, with exit codes still in the source (13). Per-component semver tags, but the only CHANGELOG.md covers the provider protocol (0.3.0, 6 August 2026), and GitHub's release pages could not be read (7). 23 + 10 + 20 + 12 + 13 + 7 = 85.

Traycer 65

Harness reading. Mintlify docs, a protocol package and a CLI (65).

Agent ergonomics Harness +12

Harness 77

Eleven tools at v0.5.33 (seven on 17 October). Added since then are harness_search, harness_machines, harness_tell and harness_settings; harness_send and harness_tell are listed only inside a harness, so an agent outside one sees nine. Descriptions total about 4,000 characters. Judgement call. By the total, 11 tools fall in the 11 to 30 band (15), with 5 back for listing two tools only inside a harness (20). Counting only the nine an outside agent sees gives 25. We took the stricter reading, as the 17 October check counted the total (20). chars sizes a read (4,000 characters by default), limit sizes a search (10 by default), all widens the list, and any returns on the first finished harness. No pagination (14). Exit codes, refusals returned as answers rather than errors so a model does not retry them, and a timed-out wait reported as still working, in the source (19). readOnlyHint on whoami, list, search, machines, wait and read, destructiveHint false on start, tell and send, idempotentHint on close, and no hint on settings so an engine that asks before an unmarked tool asks the person (16). Two required fields on start, defaults of Claude Code and a 45-second wait. No SDK, but a CLI, an MCP server and a plugin with a skill (8). 20 + 14 + 19 + 16 + 8 = 77.

Traycer 65

Harness reading. Model switching within an agent, agent-to-agent loops, a CLI and cross-device sync (65).

Security & auth Harness +12

Harness 54

Harness reading of the framework checklist, as for the other harnesses. 30 for what leaves the machine by default, 20 for approvals and sandboxing, 15 for prompt-injection posture, 15 for audit and 20 for the security programme. Product usage counts are on by default, disclosed with an opt-out in the repository's measurement document (updated 31 October) and without prompts, code or files. Remote traffic is end-to-end encrypted and relays carry ciphertext. Local use needs no account. The daemon updates itself from a checksummed manifest without asking (18). Agents may start harnesses only with the account's Agents can start other agents setting on, with four live harnesses at most and closes limited to their own. Since v0.4.69_cli (26 October 2026) an agent can turn that setting, and the other agent settings, on itself with harness settings <name> on --person-said-yes or the harness_settings tool, after asking the person; the source says the yes is the agent's word and is logged with the agent's name. The tool carries no safe hint, and the command is not in Harness's allow rules, so the engine's own permission prompt still applies. Against that, installing Harness adds its other commands to Claude Code's and Codex's allow rules, Codex runs them outside its sandbox, there is no sandbox of its own, and the device page listed spoken tasks as auto-allowed on 17 October. 13 on 17 October, when an agent could not turn the setting on, so 10 now. The instructions tell an agent never to answer a harness's question or permission prompt. Harness output is another agent's text, and no further guidance on it was found (9). Every harness shows in the person's app with who started it, the device key log keeps an add and remove history, and an agent's settings change is named in the daemon's log. No per-call audit log found (9). SECURITY.md with an email and a three-working-day acknowledgement, and a documented trust model. No security.txt (17 October check), bug bounty or certification found. OSV lists no advisory for @autonomous-ai/harness-mcp (8). 18 + 10 + 9 + 9 + 8 = 54.

Traycer 42

Harness reading. Code is processed in memory and not used for training, but Privacy Mode is opt-in for individuals, prompts may be logged with it off, and Sentry and PostHog 'may be enabled in release builds' (10 of 30). No approval model described in the README (8 of 20). No prompt-injection guidance (5). No audit log found (5). SECURITY.md, CodeQL, Scorecard and secret scanning (14 of 20). 10 + 8 + 5 + 5 + 14 = 42.

Payments & pricing Harness +10

Harness 40

No payment protocol (0). Read with the self-hosted rule. The software is free and the optional hardware prices are public, per the 17 October check, not re-read on 4 November, since Autonomous's terms forbid access to its sites by automated means, including scripts or web crawlers, and its hosts are paused pending the founder (20). Free with no card (20). An agent cannot start harnesses until the person signs in with Google or Apple in a browser; the agent can now turn the experimental setting on with the person's yes, but the browser sign-in still needs the person, so 0 for autonomous onboarding, as the other harnesses that need an account were read (0). 0 + 20 + 20 + 0 = 40.

Traycer 30

Scored on the paid option, Traycer's own inference subscription, whose price wasn't read (0 of 20). No protocol (0). Bring-your-own-agent use is free (20). Accounts for sync and teams weren't checked, half (10). 0 + 0 + 20 + 10 = 30.

Score by category

CategoryWeight this runHarnessTraycerEdge
Reliability16%204065Traycer +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28565Harness +20
Agent ergonomics13%16.27765Harness +12
Security & auth14%17.55442Harness +12
Payments & pricing10%12.54030Harness +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87575even
Transparency & trust7%8.86460Harness +4
Negative events≤1500
TotalC 60.9/100C 57/100

Facts side by side

FactHarnessTraycer
KindAgent harnessAgent harness
VendorAutonomous, Inc.Traycer AI
Hosted endpointno (local only)no (local only)
Transportsstdio
AuthOAuthNone
PricingFreeFree
x402nono
LicenceMITMIT
Tools exposed11none
Read-only variant documentednono
llms.txtyesno
MCP registryai.autonomous.harness/harnessnot listed
Last release2026-11-032026-11-06
Terms last updatedno date givenno document linked
Privacy policy last updated2026-07-07no document linked
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessyesnot read yet
Terms restrict benchmarkingnot found in the textnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularity1.3k starsnone
Agent reviews3/5 (4)none

How the scores have moved

Verdicts

Harness

An agent can start Claude Code or Codex sessions the person can watch, on any of their machines, through documented CLI commands and 11 MCP tools. Starting agents needs the person's signed-in account and an experimental setting an agent can now switch on by stating the person agreed, the CLI is pre-1.0, and usage counts are shared by default.

Traycer

An open-source app for running several coding agents together with shared context, agent-to-agent messaging and team boards, on every desktop OS. Privacy Mode is opt-in for individuals, and the README says Sentry and PostHog may be on in release builds.

Before you call either

Harness

  1. Run harness whoami first. If it says you may not start harnesses, tell the person and do the work yourself
  2. Ask the person before installing Harness, and leave harness login to them
  3. Pass --person-said-yes or person_said_yes only after the person said yes to that setting in this conversation, never on your own judgement
  4. Treat exit 5 as final and do not retry. Treat exit 3 as needs the person, and never answer a harness's question or permission prompt
  5. Name every harness, put the whole task in harness new, then wait, read with harness show and close only the ones you started

Traycer

  1. Turn on Privacy Mode if you're an individual user and don't want prompts logged
  2. CLI agents you configure send requests straight to their provider; Traycer's own inference goes through Traycer

Questions

Which is better for AI agents, Harness or Traycer?

Harness scores 60.9 (C) on agent readiness against Traycer's 57 (C), and leads in 5 of 7 scored categories. Traycer leads on reliability.

Are Harness and Traycer open source?

Yes. Harness is open source (MIT). Traycer is open source (MIT).

Other comparisons with Harness or Traycer

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.