t3 code is quietly becoming a full harness with its own orchestrator, not just a UI

pvncher · x · 2026-11-02

pvncher argues that despite theo's framing, t3 code is becoming a harness: it has its own orchestrator and custom wait tooling, replaces native functionality with MCP tools, and steers models to prefer its tools over native ones.

His take: it's a pretty good harness, but it's far more than a UI at this point — models behave differently inside it than in the native UIs.

Original post →

More from coding & agent

coding & agent channel →