▶ Watch ↗AI Engineer World's Fair 202618:59
No, That's Not a Software Factory — Ryan Cooke, WorkOS
Read the full talk →Key ideas
Scroll to read ↓WorkOS’s first sandbox could produce pull requests, but Ryan Cooke found little difference from engineers using coding agents locally. TARS and Horizon extend automation into planning, review, project coordination and context gathering—the work that turns code into a product.
- A sandbox can generate code without improving product delivery. WorkOS’s initial experience pushed it toward automating planning and coordination alongside implementation.3:21 ↗
- Ticket dependencies and completion webhooks let TARS continue a project without a fresh prompt at every handoff; requested reevaluation helps expose missing work.5:30 ↗
- Draft Hilltop documents reduce setup work and give engineers something to refine, but scope control remains an important human contribution.8:14 ↗
- An internal MCP gateway becomes more useful when it explains where information lives and when to query it. WorkOS reuses that guidance for coding, data analysis and customer analysis.12:15 ↗
- Evaluate customer delivery alongside defect rate, recovery time and voluntary adoption. Company-wide memory and session-driven improvement are future directions; authorization remains unresolved.15:27 ↗