67 sources from practitioners, by month and sentiment.
Praise centers on one app for several agents and subscriptions and on its thread sidebar. Stability is the most frequent concern, followed by the nightly build that carries the newest features and by missing team and enterprise controls.
Counted for All practitioners, from 67 sources. Change group
What practitioners praise
Every capability practitioners describe positively, ranked by how many sources say so. Open one to read who said it.
1Several Agents and Plans in One AppAll 15 sources on it praise itRunning Claude, Codex, Cursor, Grok, OpenCode or other agents side by side on the developer's own subscriptions, and moving between them.
A Codex user audits codebases with a cheaper model and has a stronger model judge and fix the findings, and uses T3 Code because it spawns threads across different harnesses.
Published Oct 29, 2026self-described: Developer describing their own use of T3 Code
Positive
Marco Ieni, Infrastructure Engineer at the Rust Foundation (Bluesky profile) (self-described)
An HN commenter who worked on Codex at OpenAI reports T3 Code is stronger on the UX side for developers than Claude and Codex, and reports they use both Codex and Claude models in it, including sub-agents between them.
Published Oct 21, 2026self-described: Former OpenAI engineer who worked on the Codex TUI
Asked how people use Claude Code and Codex together, one user runs T3 Code against several Claude and Codex instances over Tailscale through a proxy and calls it fiddly to set up but worth it.
Published Oct 19, 2026self-described: Developer describing their own use of T3 Code
Jan Marshal rotates Claude, Codex and Cursor in T3 Code, moving to the next as each usage limit runs out. He reports that while many things work well, a lot of things break constantly on the nightly build.
Published Oct 11, 2026self-described: Self-described user of multiple models at once (video)
Positive
Dara (DaraDoesCode), has an open PR to T3 Code (video) (self-described)
On Ray Fernando's stream, T3 Code user Korallis reports he burned about $12,000 of API-equivalent Claude Code and GPT usage through T3 Code in a week, all within his subscriptions. He reports that T3 Code's built-in browser cannot use the macOS keychain even on the local Mac, which makes signing in to sites painful.
Published Aug 28, 2026self-described: Runs a Linux server for work projects (stream)
Mixed
Nuno Maduro, self-described CLI user (video) (self-described)
Nuno Maduro reports T3 Code lets him use ChatGPT and Claude models in the same UI, so he can skip going to OpenCode and the Claude Code CLI. After reviewing a session he called T3 Code solid but said he would only use it if he were not a CLI devotee, so he stays on the terminal.
Published Aug 24, 2026self-described: Self-described CLI user (video)
Positive
George (georgesl.bsky.social), writes 'My AI Journey Blog' ai.georgeliu.com (Bluesky profile) (self-described)
An HN user running the nightly desktop build reports the T3 Code mobile app beats the official Claude Code mobile app and allows switching between their Claude and Codex subscriptions.
Published Aug 14, 2026self-described: Developer describing their own use of T3 Code
Jeff Escalante of Clerk, whose daily driver is the Codex desktop app, calls T3 Code his most promising bet because it runs Claude on one thread and GPT on another and could be forked.
Published Aug 13, 2026self-described: Fluid engineering role at Clerk
Robbie Palmer's accepted architecture decision record (2026-08-02) makes T3 Code the orchestrator for Claude Code, two Codex subscriptions, Grok Build and OpenCode on an always-on Mac mini driven from a phone, and rejects per-harness UIs, writing his own and hosted cloud agents. The same ADR lists the costs: T3 Code is young while the providers it wraps change quickly, remote sessions depend on one host staying up, and agent auth, pairing and network binding must all be kept working together.
Published Aug 2, 2026self-described: ML expert, full-stack builder, team lead (site meta description)
2Thread Sidebar and WorktreesAll 14 sources on it praise itThe inbox-style thread list, a git worktree per thread, and the app's feel against the vendors' own apps and terminal setups.
A developer replaced his hand-built herdr setup with T3 Code and reports his workflows and orchestration became more token-efficient, with a nicer UX across mobile, tablet and desktop.
Published Nov 1, 2026self-described: Developer describing their own use of T3 Code
Positive
HN user 9cb14c1ec0, Hacker News commenter (self-described)
An HN user who moved from cmux to T3 Code recommends it, citing worktree-per-thread spawning, steer/queue messages, the inbox-style thread list and the built-in browser.
Published Oct 21, 2026self-described: Developer describing their own use of T3 Code
Positive
joshka, former OpenAI engineer who worked on the Codex TUI (self-described)
An HN commenter who worked on Codex at OpenAI reports T3 Code is stronger on the UX side for developers than Claude and Codex, and reports they use both Codex and Claude models in it, including sub-agents between them.
Published Oct 21, 2026self-described: Former OpenAI engineer who worked on the Codex TUI
Mixed
Rasmus Wulff Jensen, self-described big Codex fan (video) (self-described)
Rasmus Wulff Jensen, a self-described big Codex fan, switched from the Codex app to T3 Code mainly for its thread sidebar and reports he can never go back. He cannot manage Codex plugins in T3 Code, which can use them as a wrapper on top of Codex, so plugin management stays in the Codex app.
Published Oct 16, 2026self-described: Self-described big Codex fan (video)
Positive
Matt Styles, Freelance software developer (Bluesky profile) (self-described)
An HN commenter reports T3 Code was mostly coded by LLMs while having a solid architectural foundation and extensive features.
Published Aug 1, 2026self-described: Freelancer/contractor (HN profile); building Jira/Discord/Teams/GitHub integrations for T3 Code (HN item 49243006)
Mixed
Branislav Mateáš, Digital analyst and developer (site bio) (self-described)
A freelance analyst and developer on Ubuntu kept T3 Code as his main interface after moving his subscription from Claude to ChatGPT, preferring it to the Codex app, which he found laggy on input. The same reviewer's remaining everyday gap was a clear view of how much subscription usage is left.
Published Jul 28, 2026self-described: Digital analyst and developer (site bio)
Better Stack's launch-week reviewer had to restart the Codex app when it lagged with several agents, and saw no lag after a few hours of multi-agent use in T3 Code.
Published Mar 7, 2026self-described: Developer describing their own use of T3 Code
Mixed
Adam (adamaoc), staff engineer (video) (self-described)
Working a real ticket on the nightly build, a self-described staff engineer saw PR creation from the app fail with an 'Invalid params' error he had seen before. He likes the app after the ticket but tells viewers not to switch from an existing tool, only to try it.
Published Aug 28, 2026self-described: Staff engineer (video)
3Remote and Phone AccessAll 11 sources on it praise itRunning agents on an always-on machine, server or isolated host and steering them from a phone, browser or another computer.
A developer replaced his hand-built herdr setup with T3 Code and reports his workflows and orchestration became more token-efficient, with a nicer UX across mobile, tablet and desktop.
Published Nov 1, 2026self-described: Developer describing their own use of T3 Code
Positive
Joe (CodingPhase), growth manager and business owner (video) (self-described)
CodingPhase's owner reports his business runs on T3 Remix, his fork of T3 Code, connected to the site's support system, courses and engagement tracking.
Published Oct 31, 2026self-described: Growth manager and business owner (video)
Asked how people use Claude Code and Codex together, one user runs T3 Code against several Claude and Codex instances over Tailscale through a proxy and calls it fiddly to set up but worth it.
Published Oct 19, 2026self-described: Developer describing their own use of T3 Code
Flavio Copes's deep dive reports T3 Code is not presented as an enterprise project-management system with centralized organization roles, shared queues, audit policy and managed compute for a large team. The same deep dive reports unattended operation on macOS needs a logged-in, awake machine and conflicts with FileVault, which makes Linux the cleaner always-on host.
Published Aug 28, 2026self-described: Maintains several websites and products (article text)
Mixed
r4lph, submitted a companion PR to T3 Code (video) (self-described)
r4lph reports that once a thread starts, T3 Code only lets him switch among the same provider's models, unlike Hermes. He runs agents on an isolated remote machine through T3 Code so they only hold the credentials he gave them.
Published Aug 21, 2026self-described: Submitted a companion PR to T3 Code (video)
An HN user running the nightly desktop build reports the T3 Code mobile app beats the official Claude Code mobile app and allows switching between their Claude and Codex subscriptions.
Published Aug 14, 2026self-described: Developer describing their own use of T3 Code
A self-described founder runs T3 Code on a persistent dev box costing under $150 a month and prompts it from laptop or phone over Tailscale, and reports the setup needed a lot of custom tooling.
Published Aug 4, 2026self-described: Founder @ www.cerebrum.com (HN profile)
Mixed
Robbie Palmer, ML expert, full-stack builder, team lead (site meta description) (self-described)
Robbie Palmer's accepted architecture decision record (2026-08-02) makes T3 Code the orchestrator for Claude Code, two Codex subscriptions, Grok Build and OpenCode on an always-on Mac mini driven from a phone, and rejects per-harness UIs, writing his own and hosted cloud agents. The same ADR lists the costs: T3 Code is young while the providers it wraps change quickly, remote sessions depend on one host staying up, and agent auth, pairing and network binding must all be kept working together.
Published Aug 2, 2026self-described: ML expert, full-stack builder, team lead (site meta description)
4Sub-agents Across AgentsAll 5 sources on it praise itOne agent starting work in another agent or model, such as Claude planning while Codex implements, or two models reviewing one pull request.
Counted for All practitioners.
Positive
Maciej Szamowski, Senior marketer who codes; building the hora calendar app (Bluesky profile) (self-described)
A marketer who codes connected his own agent to T3 Code to answer security partners' questions, handing the work to a Claude thread that already knew the repo, so his agent didn't have to dig through it.
Published Oct 30, 2026self-described: Senior marketer who codes; building the hora calendar app (Bluesky profile)
A Codex user audits codebases with a cheaper model and has a stronger model judge and fix the findings, and uses T3 Code because it spawns threads across different harnesses.
Published Oct 29, 2026self-described: Developer describing their own use of T3 Code
Positive
Marco Ieni, Infrastructure Engineer at the Rust Foundation (Bluesky profile) (self-described)
Ras Mic reports Orchestrator V2 lets him move work to Claude when his Codex usage limit runs out. He warns that the features he relies on need the nightly build, where things can change or break.
Published Oct 21, 2026self-described: Developer describing their own use of T3 Code
Positive
joshka, former OpenAI engineer who worked on the Codex TUI (self-described)
An HN commenter who worked on Codex at OpenAI reports T3 Code is stronger on the UX side for developers than Claude and Codex, and reports they use both Codex and Claude models in it, including sub-agents between them.
Published Oct 21, 2026self-described: Former OpenAI engineer who worked on the Codex TUI
Every concern practitioners raise, most raised first.
1Crashes, Regressions and Lost StateAll 8 sources on it raise it as a concernCrashes, crash loops, threads that disappear after an update, lost logins or context, and slow runs.
After the in-app update to 0.1.0, one user's thread list dropped 24 recent threads without an error; the reporter found the data still on disk and recovered it by re-seeding the new database.
Published Oct 16, 2026self-described: Developer describing their own use of T3 Code
Negative
deepontology, GitHub issue author on pingdotgg/t3code
On a nightly build, a user measured 156 ms average fsync on his disk and found Orchestrator V2's per-delta event writes stalled the server and dropped clients after about an hour with five concurrent runs.
Published Oct 4, 2026self-described: Developer describing their own use of T3 Code
Mixed
Adam (adamaoc), staff engineer (video) (self-described)
Working a real ticket on the nightly build, a self-described staff engineer saw PR creation from the app fail with an 'Invalid params' error he had seen before. He likes the app after the ticket but tells viewers not to switch from an existing tool, only to try it.
Published Aug 28, 2026self-described: Staff engineer (video)
A two-week user reported periodic T3 Code crashes after a macOS update when running four or five subagents, and switched back to Claude Code in the terminal.
Published Aug 25, 2026self-described: Developer describing their own use of T3 Code
Negative
Khannor-PS, GitHub issue author on pingdotgg/t3code
A user running three Claude Max accounts in T3 Code on macOS reported five incidents in 12 days where the stored Claude OAuth credentials were emptied after T3 or Claude CLI updates, forcing a full re-login each time.
Published Aug 10, 2026self-described: Developer describing their own use of T3 Code
Jan Marshal rotates Claude, Codex and Cursor in T3 Code, moving to the next as each usage limit runs out. He reports that while many things work well, a lot of things break constantly on the nightly build.
Published Oct 11, 2026self-described: Self-described user of multiple models at once (video)
Mixed
Robbie Palmer, ML expert, full-stack builder, team lead (site meta description) (self-described)
Robbie Palmer's accepted architecture decision record (2026-08-02) makes T3 Code the orchestrator for Claude Code, two Codex subscriptions, Grok Build and OpenCode on an always-on Mac mini driven from a phone, and rejects per-harness UIs, writing his own and hosted cloud agents. The same ADR lists the costs: T3 Code is young while the providers it wraps change quickly, remote sessions depend on one host staying up, and agent auth, pairing and network binding must all be kept working together.
Published Aug 2, 2026self-described: ML expert, full-stack builder, team lead (site meta description)
2New Features Ride the NightlyAll 8 sources on it raise it as a concernThe features reviewers rely on shipping first in nightly builds, where behavior changes or breaks.
An HN user who uses T3 Code as an agent orchestrator reports its nightly release is a rolling five-hour release with many users, nothing really breaks, and a handful of maintainers merge 100 to 200 PRs a day.
Published Oct 25, 2026self-described: Developer describing their own use of T3 Code
Professor LoulouLon's V2 review concludes that teams using one lab and wanting cloud runs or official support are safer on that lab's own app, and that V2 was nightly-only. The same review notes usage telemetry is on by default and can only be turned off with an environment variable.
Published Oct 14, 2026self-described: Developer describing their own use of T3 Code
Negative
deepontology, GitHub issue author on pingdotgg/t3code
On a nightly build, a user measured 156 ms average fsync on his disk and found Orchestrator V2's per-delta event writes stalled the server and dropped clients after about an hour with five concurrent runs.
Published Oct 4, 2026self-described: Developer describing their own use of T3 Code
Mixed
Adam (adamaoc), staff engineer (video) (self-described)
Working a real ticket on the nightly build, a self-described staff engineer saw PR creation from the app fail with an 'Invalid params' error he had seen before. He likes the app after the ticket but tells viewers not to switch from an existing tool, only to try it.
Published Aug 28, 2026self-described: Staff engineer (video)
Ras Mic reports Orchestrator V2 lets him move work to Claude when his Codex usage limit runs out. He warns that the features he relies on need the nightly build, where things can change or break.
Published Oct 21, 2026self-described: Developer describing their own use of T3 Code
Mixed
Jan Marshal, self-described user of multiple models at once (video) (self-described)
Jan Marshal rotates Claude, Codex and Cursor in T3 Code, moving to the next as each usage limit runs out. He reports that while many things work well, a lot of things break constantly on the nightly build.
Published Oct 11, 2026self-described: Self-described user of multiple models at once (video)
3No Team or Enterprise ControlsAll 8 sources on it raise it as a concernOrganization roles, audit policy, managed installs, single sign-on, compliance-bound providers and telemetry defaults a company environment needs.
Counted for All practitioners.
Negative
MarvelTiyjudy, GitHub issue author on pingdotgg/t3code
A user on a corporate-managed Windows 11 Enterprise machine without admin rights reported T3 Code's in-app update failing three times in two days, leaving the old version running.
Published Oct 26, 2026self-described: Developer describing their own use of T3 Code
Negative
causercode, GitHub issue author on pingdotgg/t3code
On a corporate-managed Windows 11 machine with endpoint security, T3 Code's in-app update silently failed because the installer signature check exceeded a 20-second timeout; the same nightly updated fine on a personal machine.
Published Oct 16, 2026self-described: Developer describing their own use of T3 Code
T3 Code's integrated browser blocked Okta FastPass sign-in for a GitHub Enterprise Cloud org that enforces Okta SSO, because it offered no way to grant local network access.
Published Sep 4, 2026self-described: Developer describing their own use of T3 Code
Mixed
Flavio Copes, maintains several websites and products (article text) (self-described)
Flavio Copes's deep dive reports T3 Code is not presented as an enterprise project-management system with centralized organization roles, shared queues, audit policy and managed compute for a large team. The same deep dive reports unattended operation on macOS needs a logged-in, awake machine and conflicts with FileVault, which makes Linux the cleaner always-on host.
Published Aug 28, 2026self-described: Maintains several websites and products (article text)
Professor LoulouLon's V2 review concludes that teams using one lab and wanting cloud runs or official support are safer on that lab's own app, and that V2 was nightly-only. The same review notes usage telemetry is on by default and can only be turned off with an environment variable.
Published Oct 14, 2026self-described: Developer describing their own use of T3 Code
Mixed
Robbie Palmer, ML expert, full-stack builder, team lead (site meta description) (self-described)
Robbie Palmer's accepted architecture decision record (2026-08-02) makes T3 Code the orchestrator for Claude Code, two Codex subscriptions, Grok Build and OpenCode on an always-on Mac mini driven from a phone, and rejects per-harness UIs, writing his own and hosted cloud agents. The same ADR lists the costs: T3 Code is young while the providers it wraps change quickly, remote sessions depend on one host staying up, and agent auth, pairing and network binding must all be kept working together.
Published Aug 2, 2026self-described: ML expert, full-stack builder, team lead (site meta description)
GILD's fact checks, which don't count as sources
Checked Nov 1, 2026.T3 Code's docs state that product usage data, tied to a hashed account or installation identifier, is on by default and turns off with T3CODE_TELEMETRY_ENABLED=false. T3 Code docs: Telemetry
4Missing Features Against Vendor AppsAll 5 sources on it raise it as a concernPlugin management, side chats, scheduling, live sub-agent views or model switching that a developer had in another app.
Counted for All practitioners.
Mixed
HN user CharlieDigital, Hacker News commenter (self-described)
A Hacker News commenter who uses Paseo wrote that Paseo is Apache 2.0 and T3 Code MIT, that T3 Code had no docs site, and quoted a T3 Code repository doc saying a T3 Connect account links up to 3 machines, raised by paid T3 Chat plans, while Paseo's relay has no limits.
Published Oct 31, 2026self-described: Hacker News commenter
A user who runs several Codex accounts through a CLI proxy with T3 Code reports features such as image generation skills break in that setup, and that their Claude accounts were banned after trying the same with Claude.
Published Oct 1, 2026self-described: Developer describing their own use of T3 Code
Mixed
r4lph, submitted a companion PR to T3 Code (video) (self-described)
r4lph reports that once a thread starts, T3 Code only lets him switch among the same provider's models, unlike Hermes. He runs agents on an isolated remote machine through T3 Code so they only hold the credentials he gave them.
Published Aug 21, 2026self-described: Submitted a companion PR to T3 Code (video)
Mixed
Michael Chernigin, rust dev (Bluesky profile) (self-described)
Rasmus Wulff Jensen, a self-described big Codex fan, switched from the Codex app to T3 Code mainly for its thread sidebar and reports he can never go back. He cannot manage Codex plugins in T3 Code, which can use them as a wrapper on top of Codex, so plugin management stays in the Codex app.
Published Oct 16, 2026self-described: Self-described big Codex fan (video)
Statements this group's sources agree on, then the ones close to agreement.
For all practitioners, no statement reaches 5 sources from 3 authors.
Where it disagrees
Questions the sources split on, with the count on each side.
Evidence remains mixed
Run agents through T3 Code, or through each vendor's own app?
63
T3 Code, 6 sources
Some moved from the Codex or Claude apps to T3 Code for its sidebar, its mobile app and running several vendors' agents in one place.
The vendor's own app, 3 sources
Others stayed with or went back to the vendor's app or terminal, citing speed, crashes, or a team that uses only one lab.
Evidence remains mixed
T3 Code, or another agent app such as Paseo, Orca, OpenChamber, Conductor or herdr?
34
T3 Code, 3 sources
Some chose T3 Code over cmux, a hand-built setup or Orca in head-to-head use.
Another agent app, 4 sources
Others prefer Paseo, Orca, OpenChamber, Conductor or herdr for fewer bugs, more control or a different license.
The evidence
Whose experience this is
The three groups, then every practitioner by the context they work in, and how emphasis changes with scale.
Three groups drawn from the same sources. Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. Signals open on All practitioners. Leaders and teams have 5 accounts; GILD prints their sentiment from 20.
Engineering leaders and teams
5 sources. These accounts come from founders and engineers speaking for a company or team: always-on hosts, pull request review across two models, and whether T3 Code fits a team at all.
Individual builders
62 sources. These accounts emphasize running several agents and subscriptions in one app, the thread sidebar, remote access, and what breaks between builds.
All practitioners
67 sources. This count includes every practitioner: individual builders and the team and leadership accounts together.
67 sources from practitioners, by the context they work in. Filled rows count for this group.
Individual practitionerSolo developers and independent builders62 sources, counted here
Emphasizes Several agents and plans in one app, the sidebar, and what breaks between builds
Very small team2 to 10 people, or a team of unstated size2 sources, counted here
Emphasizes A small business running on a fork, and a founder weighing agent apps
Professional team11 to 50 engineers, or a named company's team2 sources, counted here
Emphasizes Two-model pull request review and agent apps beside a vendor's own
Technical leadershipLeaders setting adoption across teams1 sources, counted here
Emphasizes Always-on hosts reached from anywhere
Organization-wideEnterprise or company-wide rolloutNo sources from this setting yet
What changes with scale. Individual developers adopt T3 Code to run several agents and plans side by side and leave it over crashes or features that wait on the nightly build. Accounts from inside companies stop at a person's own setup: corporate-managed Windows machines, single sign-on in the built-in browser and compliance-bound providers are where it runs into a company environment.
Where the sources come from
Where this group's sources were published.
Counted for All practitioners, from 67 sources. Change group
73 sources for this group, 6 of them documentation
Developer Communities42, 58% of 73 sources
Videos & Podcasts20, 27% of 73 sources
T3 Code Documentation6, 8% of 73 sources
Engineering Blogs & Reviews5, 7% of 73 sources
Older evidence is retained when it still applies. Accounts of the March alpha, early 0.0.x releases and limits Orchestrator V2 removed stay in the record, marked Superseded or Needs a recheck.
Builds the T3 Code evidence base from public pages: each account names its author and publication date and is coded from an exact quote on the page.
Shows a finding only when at least 5 sources from 3 different authors discuss it, and a disagreement only with at least 2 sources on each side.
Nov 1, 2026: every record checked by a second model against its stored page before it entered the count.
Method
A running review of what engineering teams report about T3 Code, from individual builders to engineering leaders. Each finding links to its sources, and each conflict shows both sides.
Counts cover only the sources GILD reviewed.
Who counts
Engineering leaders and teams
Very small team, Professional team, Technical leadership, Organization-wide
Individual builders
Individual practitioner
All practitioners
Everyone in the leaders and teams and individual builders groups
Choose a group to select whose experience counts. Within that group, each author counts once in the practitioner sentiment, with their latest view. GILD files each source in a group from how the account describes its author. A role or employer marked self-described is what the source states about themselves. Documentation checks facts for every group and never counts toward sentiment.
How the numbers work
Overall signal. Positive votes minus negative ones, per 100 votes from the sources that take a side. Each author counts once, with their latest view, whoever they are and wherever they posted. The older weighted reading, where accounts GILD matched to a named person count three times when GILD lists the author among engineering leaders and twice otherwise, is shown beside it as a second view. Where an author wrote more than one source, the line beside the split gives the votes, one per author, so the score follows from it. When one author's sources from the same day disagree, that author counts as mixed, and a half point rounds away from zero. Sources with no opinion are listed and not counted. Strong positive is +50 or higher, positive +20 to +49, mixed −19 to +19, negative −20 to −49, strong negative −50 or lower.
Weighted reading, second view. Counted the older way, where an account GILD matched to a named person counts two or three times, all practitioners read +22 positive (method sentiment/S1). GILD printed that number as "GILD score" until October 29, 2026; most of those matches rest on a name or a self-described role.
Unscored. A group gets a score only with 20 sources from 15 authors. Below that, one source moves the score about 5 points, so the read says "Unscored until 20 sources from 15 authors" and shows its counts.
Independence. A source whose author works for the vendor, for one of its partners or programs, or for a competitor, and a page the vendor published or ran, is listed with that tie and counts toward nothing. One author counts on at most two records per product. The line under the score says how many authors and how many separate discussions the counted sources come from: comments in one thread are one discussion.
Praise and concerns. How many of the sources that discuss a theme praise it or raise it.
Consensus. A statement joins when 20% of the group's sources support it and fewer contradict it. Contradicting sources are counted separately. Below that line a statement shows as building. At 40% or more it reads Strong agreement; below, Recurring point.
Disagreements. The count on each side. GILD names no winner and gives no share of all users.
Minimum evidence. A finding needs 5 sources from 3 authors; a disagreement also needs 2 on each side. Smaller counts stay in the table below, marked under the minimum.
Labels on a source
A source's date and whether it still applies are separate: a recent post can describe an old version, and an old one can still hold.
Documented
Stated in official documentation.
Reported
A practitioner's account of their own use.
Measured
Backed by the source's own measurements, such as a comparative test or tracked team metrics.
GILD analysis
GILD's check of a claim against official documentation.
Current
Describes the product as it is now.
Still applicable
Older, and the behavior or lesson still holds.
Needs a recheck
May depend on a plan, version or setting that changed since it was written. It keeps counting until GILD rechecks it, since the rest of the account usually holds, and its card says so.
Out of date
No longer accurate. Kept in the record; counts toward nothing current.
Flagged for a recheck, of the sources that take a side: leaders and teams 0 of 5, individual builders 11 of 49, all practitioners 11 of 54.
Limits
These figures come from 67 public accounts from Hacker News, GitHub issues, Reddit, Bluesky, blogs, YouTube reviews and a podcast; the 2 by contributors to the project count toward nothing. T3 Code is young and most accounts come from individual developers; team and leadership accounts are few. Theo Browne and other T3 Tools staff are left out because they make the product. This is not a representative survey.
Sources span T3 Code's March 2026 alpha through v0.1.6 and the nightly builds of October 2026. Accounts of an alpha, an early 0.0.x release or a limit fixed since are marked Superseded or Needs a recheck.
Every count, and the sources behind it
18 findings for 3 groups
Each row opens its sources for the group you are reading.
GILD's checks of claims against official documentation, kept apart from the source counts.
No Team or Enterprise Controls. T3 Code's docs state that product usage data, tied to a hashed account or installation identifier, is on by default and turns off with T3CODE_TELEMETRY_ENABLED=false. T3 Code docs: Telemetry, checked Nov 1, 2026
Claude Logins and Limits. T3 Code's FAQ says it drives Claude through Anthropic's Agent SDK and that this drains 5-hour limits faster than Claude Code directly, which it calls a bug on Anthropic's side. T3 Code docs: FAQ, checked Nov 1, 2026