Garry Tan Built a 24/7 AI Engineering Team for Free
Garry Tan Built a 24/7 AI Engineering Team for Free
Don’t miss what’s happening
Article
Conversation
Garry Tan Built a 24/7 AI Engineering Team for Free
GStack Isn’t a Coding Tool. It’s the First Real Software Factory for the AI Era. For the last decade, startups scaled by hiring. More engineers. More designers. More PMs. More process. More meetings. That was the formula. Then one sentence quietly broke the entire model. «“I don’t think I’ve typed like a line of code probably since December.” — Andrej Karpathy, March 2026» That sentence should terrify every software company operating like it’s still 2021. Because the bottleneck is no longer typing code. The bottleneck is orchestration. And Garry Tan just open sourced one of the clearest blueprints we’ve seen for what software development looks like after AI-native workflows fully arrive. The project is called gstack. At first glance, it looks like another “AI coding toolkit.” It is not. It’s something much bigger: A structured operating system for turning one person into an AI-native product organization. The Most Important Shift Isn’t AI Writing Code Everyone is focused on the wrong thing. The interesting part is not that AI can generate code. GitHub Copilot already proved that years ago. The real shift is this: AI is starting to replace coordination overhead. That’s the actual revolution. Historically, software teams scaled poorly because human coordination is expensive. As products become more complex, companies add: architecture reviews QA layers security reviews design systems release managers sprint rituals documentation processes deployment gates The problem is that every layer slows shipping velocity. So startups faced a tradeoff: Move fast → create chaos Add process → become slow GStack attacks that exact problem. Not by removing process. But by automating it. GStack Turns AI Into a Structured Company Most people use AI coding tools like smarter autocomplete. GStack treats AI differently. It treats AI like a team. That’s the breakthrough. Instead of one generic assistant trying to do everything, GStack splits the workflow into specialized operational roles: CEO Staff Engineer QA Lead Security Officer Designer Release Engineer DevEx Reviewer SRE Technical Writer Each role has its own context, standards, rules, and responsibilities. Not vague prompting. Structured operational behavior. That sounds simple. But it fundamentally changes output quality. Because most AI-generated software fails for the same reasons humans fail: unclear requirements bad architecture scope creep weak testing missing edge cases poor UX undocumented decisions no verification loop GStack doesn’t just generate code. It creates a system that forces those conversations to happen automatically. That is an entirely different category of tooling. The Most Important Command Might Be /office-hours This is where the philosophy becomes obvious. One of GStack’s core workflows is /office-hours. Not /build-feature. Not /generate-code. /office-hours. That’s intentional. Before implementation starts, the system interrogates the product idea itself. Not hypotheticals. Not surface-level brainstorming. Real forcing questions. Pain points. User behavior. Hidden assumptions. Scope traps. Market positioning. Failure modes. The AI pushes back. Challenges framing. Rewrites the problem definition. Sometimes the output is: «“You don’t need a feature. You need a different product.”» That sounds closer to a YC partner conversation than a coding assistant. And that’s exactly the point. AI Coding Has a Massive Reliability Problem Most people experimenting with “vibe coding” eventually hit the same wall: The demo works. Production breaks. AI is excellent at creating software that looks complete. That’s dangerous. Because surface polish hides operational fragility. This is why GStack’s most underrated innovation is probably not code generation. It’s verification layers. Commands like: /review /qa /cso /benchmark /ship exist because AI-generated code needs aggressive validation. The QA flow is especially important. GStack launches a real browser using Playwright and actually tests the application like a human would. Clicks buttons. Navigates flows. Finds broken states. Generates regression tests. That changes the equation completely. The industry is slowly realizing something critical: The future isn’t “AI writes code.” The future is: «AI writes code AI reviews code AI tests code AI debugs code AI ships code» End-to-end autonomous software operations. GStack is one of the first serious open-source systems attempting that full stack. The Real Insight: Process Beats Prompting This may be the biggest lesson from the entire project. Most people still think AI productivity comes from writing better prompts. But prompting is not the moat. Process is. A mediocre prompt inside a strong operational system beats a brilliant prompt inside chaos. That’s why GStack matters. It encodes workflow discipline directly into the development lifecycle. Think → Plan → Build → Review → Test → Ship → Reflect That structure sounds boring. But historically, process is what separates: hobby projects from products prototypes from companies demos from production systems The difference now is that AI can execute large portions of the process itself. That’s new. And very important. One Person Companies Are Becoming Real For years, “one-person unicorn” sounded like Silicon Valley fantasy. Not anymore. When Garry Tan says he shipped: 3 production services 40+ features while running YC full-time the important part is not whether AI wrote the code. The important part is leverage. AI-native builders now operate with dramatically amplified execution capacity. The limiting factor is no longer: «“Can I code this?”» It’s: «“Can I coordinate systems effectively?”» That’s a massive shift in what technical entrepreneurship means. The highest leverage founders increasingly look less like programmers and more like orchestrators. People who: define systems manage workflows make taste decisions validate direction coordinate AI agents maintain product vision The role of the builder is evolving upward. GStack Feels Like the First Post-Copilot Framework Copilot helped developers code faster. GStack tries to help developers operate faster. That distinction matters. Because the bottleneck in modern software isn’t syntax speed anymore. It’s: context switching coordination validation product thinking debugging deployment confidence GStack is trying to compress the entire operational surface area of software creation. And it’s doing it through composable AI workflows. That’s why this project is getting attention far beyond Claude users. It supports: Claude Code Codex CLI Cursor Gemini OpenClaw multiple browser agents persistent memory systems multi-agent coordination This is starting to resemble infrastructure. Not tooling. Infrastructure. The Browser Layer Is a Bigger Deal Than People Realize One of the most underrated parts of the project is the browser subsystem. Most AI agents are effectively blind. They operate through static context. GStack gives them persistent browser state. That means: authenticated sessions long-lived workflows real navigation live debugging multi-tab operations browser handoffs coordinated agent browsing That sounds small until you realize: A huge percentage of human software work happens inside browsers. QA. Admin panels. CMS tools. Dashboards. Third-party integrations. Deploy platforms. Analytics. Giving AI persistent browser capability dramatically expands operational usefulness. This is the beginning of AI agents moving from: «“helpful autocomplete”» to: «“active operational workers.”» Open Source Is the Strategic Move The smartest thing Garry Tan did may have been making GStack MIT licensed. Because this space is evolving too quickly for closed systems to dominate through features alone. Open ecosystems compound faster. Developers will: create custom skills add workflows improve orchestration expand integrations build domain-specific pipelines That creates a network effect around methodology. Not just software. And methodology is where the real value lives. We’re Watching the Software Org Chart Collapse The software industry is entering an uncomfortable phase. Not because engineers disappear. But because organizational structures are changing faster than most companies expect. A founder with: strong product taste AI-native workflows autonomous review systems browser agents deployment automation persistent memory can now execute at a level that previously required entire teams. That doesn’t eliminate engineering. It changes what engineering organizations optimize for. The winners won’t be the companies with the most developers. They’ll be the companies with the best AI operational systems. That’s the real story behind GStack. Not “AI writes code.” But: «software development itself is becoming programmable.» And once process becomes programmable, leverage explodes. The companies built over the next five years will look fundamentally different from the companies built over the last fifteen. GStack is one of the clearest early glimpses of that future.