In 30 seconds
Theo recalls creating the T3 stack to support his preferred way of building applications. He wanted errors to be visible across frontend and backend boundaries, and says his desire to make that setup easy to share helped lead to his channel.
- 1Before the AI videosTheo recalls create-t3-app and says the stack began as a way to build apps more easily.
- 2Errors across boundariesHe was frustrated when frontend code could not reveal that a backend change had caused a mismatch.
- 3A small set of abstractionsHe wanted full-stack type safety with minimal effort and a setup that was easy to share.
Takeaways
- Theo created the T3 stack to make his preferred app-building workflow easier.
- He wanted the computer to catch mistakes across frontend and backend boundaries.
- Minimal abstractions and full-stack type safety were central to the goal.
- Sharing the setup without repeatedly explaining it helped inspire the channel.
Read the edited text by chapter
The problem behind T3
Theo recalls create-t3-app and the workflow he wanted. He describes the difficulty of detecting errors across system boundaries.
Some of you remember me from create-t3-app, before the channel focused so much on AI. The T3 stack wasn't an attempt to make my technology take over the world. I wanted an easier way to build apps in the particular lazy style I liked.
I wanted my computer to tell me when I made mistakes across the boundaries in my systems. My backend could catch errors between its own functions, but it frustrated me that the frontend couldn't tell when a backend change caused a problem.
A simpler full-stack setup
The stack aimed to make type safety easier with minimal abstractions. Theo explains how sharing that approach helped lead to his channel.
The T3 stack was an attempt to rethink that with a minimal set of abstractions: give me full-stack type safety so the computer can catch my mistakes, with less effort. My belief that others should use a setup like this, impatience with explaining it repeatedly and desire to put it in one place helped lead to this channel.
More from this channel
38:47EN
Theo - t3․gg· Oct 28, 2026Theo’s Long-Running Agent Experiments: Verification, Compute and CostTheo Browne · Ping LabsA skateboard game and two compiler projects show how repeated checks and flexible compute can sustain agent work—and how expensive those loops can become.
36:07ENTheo - t3․gg· Oct 27, 2026Theo on Token Costs, Coding Agents, and the Price of AI CapabilityTheo Browne · Ping LabsA viral estimate of Lauren's AI spending prompts a closer look at cache pricing, benchmarks, and the changing work of coding agents.
30:37ENTheo - t3․gg· Oct 26, 2026Theo’s Three Skills for Reviewing and Shipping with Coding AgentsTheo Browne · Ping LabsHow sol-loop, full-send and full-stop encode review, verification and different levels of merge authority.
0:43ENTheo - t3․gg· Oct 23, 2026Theo Distinguishes Security Vulnerabilities from Active AttacksTheo Browne · Ping LabsA short explanation of why disclosed software flaws and reported attacks are different kinds of security news.
29:22ENTheo - t3․gg· Oct 22, 2026Theo on Security Vulnerabilities, Stolen API Keys and AITheo Browne · Ping LabsA look at the gap between vulnerability disclosure and patching, and a speculative account of why stolen inference keys may be valuable.
31:13ENTheo - t3․gg· Oct 20, 2026Theo on Why Smarter Models Help More Than DevelopersTheo Browne · Ping LabsFrom game modifications to compiler experiments, Theo revisits his assumptions about who benefits from more capable AI.