Head to head · Agent harnesses · October 2026 research run

Conductor vs T3 Code

T3 Code scores 51.9 (D) on agent readiness against Conductor's 41.3 (E), and leads in 4 of 7 scored categories. Conductor leads on schema & documentation and security & auth. Both do agent harnesses.

Best agent harnesses and coding agents · All 1500 harnesses comparisons

Which one, for what

Conductor E

Best for Existing Conductor users planning their move before Cloud closes on 20 November 2026 and the local app winds down in early 2027.

Ahead on

  • Schema & documentation, 60 against 55
  • Security & auth, 45 against 35

Watch for

No new downloads or sign-ups since 4 November 2026

T3 Code D

Best for Developers who want one app, including on their phone, to drive several coding agents they already pay for.

Ahead on

  • Reliability, 43 against 25
  • Agent ergonomics, 60 against 55
  • Payments & pricing, 60 against 0
  • Maintenance & community, 75 against 58

Also in its favour

  • No key needed to call it
  • Open source

Watch for

Usage data on by default, with hashed OpenAI and Claude account identifiers, and relay traces to Axiom

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.

Payments & pricing T3 Code +60

Conductor 0

No new sign-ups since 4 November, free users can't upgrade, and no price is shown. No protocol, no published price, no open free tier, no onboarding (0).

T3 Code 60

Free self-hosted software with nothing to buy, so 0 for a protocol and 20 each for public pricing, a free tier and onboarding with no sign-up, 60.

Reliability T3 Code +18

Conductor 25

Read as local software that is winding down. Installed from Conductor's own download, which stopped taking new users on 4 November 2026 (10). Closed source, so no public CI or issue tracker (0, 0). A dated changelog, newest 0.93.0 on 4 November (15). Version 0.93 (0). 10 + 0 + 0 + 15 + 0 = 25.

T3 Code 43

Local software. An install script and desktop and mobile apps from the vendor (20). ci.yml and windows-tests.yml 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). Stable tags v0.1.5 to v0.1.7 with many nightlies, no changelog file (8). Version 0.1.7 (0). 20 + 15 + 0 + 8 + 0 = 43.

Maintenance & community T3 Code +17

Conductor 58

0.93.0 on 4 November 2026 (30). Several dated releases in 90 days, per the changelog index (20). Discord, a subreddit and email for support (8). Closed app, no package or CI to read (0). 30 + 20 + 8 + 0 + 0 = 58. The local app gets new models and critical fixes only until early 2027.

T3 Code 75

Commits and nightly tags on 6 November 2026 (30). More than three releases in 90 days (20). GitHub issues and pull requests weren't read (GitHub's pages refuse these sessions), so that line is scored absent (0). Current official apps and install script (15). CI on push (10). 30 + 20 + 0 + 15 + 10 = 75.

Security & auth Conductor +10

Conductor 45

Closed app. Telemetry and data handling weren't read beyond the transition notice (10 of 30). A security and permissions page (10 of 20). No prompt-injection guidance found (5). No audit log found (5). SOC 2 Type II report at trust.conductor.build (15 of 20). 10 + 10 + 5 + 5 + 15 = 45.

T3 Code 35

Harness reading. Product usage events go by default to ingest.t3.codes and PostHog, with hashed identifiers for your T3 Connect, OpenAI and Claude accounts, and relay traces to Axiom, which can include machine names and error text. Off with T3CODE_TELEMETRY_ENABLED=false or a managed policy. Disclosed in docs/user/telemetry.md, not the README (10 of 30). Permission modes and managed policies (12 of 20). No prompt-injection guidance (5). No audit log (5). No security policy file found (3). 10 + 12 + 5 + 5 + 3 = 35.

Schema & documentation Conductor +5

Conductor 60

Harness reading. Docs for workspaces, review and merge, a Conductor API reference page linked from the docs (not read), and security and permissions pages (60).

T3 Code 55

Harness reading. User docs in the repository (managed policy, handoffs, providers, telemetry), AGENTS.md for contributors, a server other clients connect to (55).

Agent ergonomics T3 Code +5

Conductor 55

Harness reading. Each task gets a workspace, branch, terminal and diff, with pull requests and merges from the app, and an API for integrations; not re-read in detail (55).

T3 Code 60

Harness reading. Remote control from phone or browser, portable handoffs between providers and managed policies for teams (60).

Score by category

CategoryWeight this runConductorT3 CodeEdge
Reliability16%202543T3 Code +18
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.26055Conductor +5
Agent ergonomics13%16.25560T3 Code +5
Security & auth14%17.54535Conductor +10
Payments & pricing10%12.5060T3 Code +60
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.85875T3 Code +17
Transparency & trust7%8.85351Conductor +2
Negative events≤1500
TotalE 41.3/100D 51.9/100

Facts side by side

FactConductorT3 Code
KindAgent harnessAgent harness
VendorConductor (joining Meta)T3 Tools Inc.
Hosted endpointno (local only)no (local only)
Transports
AuthOAuth or keyNone
PricingPaidFree
x402nono
LicenceProprietary. A closed-source Mac app and hosted Conductor Cloud under Conductor's termsMIT
Read-only variant documentednono
llms.txtnono
Last release2026-11-042026-11-06
Terms last updatednot read yetno document linked
Privacy policy last updatednot read yetno document linked

Verdicts

Conductor

Conductor ran parallel coding agents on the Mac, and Meta is acquiring it. It has taken no new users since 4 November 2026, Cloud turns read-only on 13 November and shuts down on 20 November, and the local app winds down in early 2027, when all user data is deleted.

T3 Code

A fast-moving open-source way to run and steer several coding agents from desktop, browser or phone, using the subscriptions you already have. It's pre-1.0, and it sends usage data by default, including hashed identifiers for your OpenAI and Claude accounts, with the opt-out documented outside the README.

Before you call either

Conductor

  1. Export your data from Settings, Account, Export data before 20 November 2026
  2. Move Cloud workspaces to your Mac with Transfer to local before 13 November
  3. Plan a move off the local app before early 2027; see the agent-harnesses category for alternatives

T3 Code

  1. Set T3CODE_TELEMETRY_ENABLED=false before starting the server if you don't want usage events sent
  2. Install and log in to at least one provider CLI first, such as codex login or claude auth login
  3. Use a managed policy to fix settings across a team

Questions

Which is better for AI agents, Conductor or T3 Code?

T3 Code scores 51.9 (D) on agent readiness against Conductor's 41.3 (E), and leads in 4 of 7 scored categories. Conductor leads on schema & documentation and security & auth.

Are Conductor and T3 Code open source?

No open-source release is listed for Conductor. T3 Code is open source (MIT).

Other comparisons with Conductor or T3 Code

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.