Parallax vs T3 Code

Parallax 30

No x402, MPP or L402 (0). Parallax episode credit prices are read from the account after sign-in. Gateway token prices are public at GET /v1/catalog with no key, which covers Conifer credit spent by agents (10). $50 of Conifer credit and 5 free episodes on GitHub sign-up, with no card mentioned, and agents can run on the owner's own Claude and Codex subscriptions (20). A person has to download the app, sign in and install the GitHub App, so no autonomous 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.

Parallax 29

The review API has no OpenAPI or endpoint reference. Endpoints appear only in curl examples, and the base URL $PARALLAX_URL is not published (0). conifer.build/llms.txt covers the gateway in detail and Parallax in two lines that point to the docs (5). The docs explain sessions, sweeps, evidence states, memory and retention at length, but nothing documents the app, Captain, fallback or fast merge (8). parallax.yml keys are listed with allowed values (deliver: proven-only, review: off, severity floors, sweep modes), but request and response shapes for the API are not (5). curl examples, sample sweep lines and a table of skip reasons with the fix for each (8). Paths sit under /v1, with no changelog for Parallax (3).

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).

Parallax 56

v1.0.2 on 16 October 2026 (30). Three releases, v1.0.0 to v1.0.2, on 15 and 16 October 2026 (20). Closed service. No public changelog. Support through a GitHub issues link, a Discord server and email, none of which we could check for replies (3). No Parallax SDK and nothing in the MCP registry. Conifer's SDK is for the gateway (0). Signed builds with checksums and a self-updater, with no CI to inspect (3).

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.

Parallax 42

Scored on the review API and the hooks, the only parts an agent touches. The session-start brief is cut at 6,000 characters, memory per review call at 12,000, and lesson_cap sets 1 to 20 lessons per person (8). repo filters on recall and brief, brain=true on the ledger, no documented pagination (4). Skip reasons such as capture_commit_missing and test_configuration_missing each come with a fix, but HTTP error codes for the API are not documented (12). A session is swept once per capture mark, retries use no extra credit, and a fix PR is reused and never reopened or merged by Parallax (14). No SDK for Parallax, and capture of every repository is the default (4).

T3 Code 60

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

Parallax 43

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. Once installed, capture uploads transcripts, tool calls with results and source snapshots from every repository on the machine unless a local allowlist is set first, and the app updates itself by default. Uploads stop with PARALLAX_STORE_UPLOAD=off and the token is revocable (8). Proofs run in a throwaway cloud copy, automatic PR review is off by default and Parallax never merges its own fix PR. What Captain may do to a running agent is not documented (10). Reviewers read untrusted transcripts and code with no documented mitigation. Lessons injected into the agent come only from verified outcomes and maintainer replies, never bots, and the brief labels everything else as cited fact (8). Recall receipts, per-injection records, sweep lines, the review ledger and GET /v1/calibration (12). No security.txt, bug bounty, SOC 2 or advisories. The privacy policy names a contact for security reports with a two-business-day reply and lists encryption and row-level security (5).

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.