Ross says models had reached a capability threshold for handling the software lifecycle, but company development had not yet accelerated as expected. He frames the gap as a problem of implementation, architecture, and orchestration, and asks how far agents could go if given a greenfield project. The project tested whether agents could build and operate software continuously, with no token budget constraint.
No Token Budget: Agentic Software Factories on Kubernetes
Speaker
Carl Ross, a member of technical staff at OpenAI, discusses agentic software factories on Kubernetes at Agent Conf 2026, on the Callstack channel.
The architecture models agents and deterministic processes as actors with unique identities, behaviors, and inboxes. Actors communicate through three actions: tell another actor something, spawn an actor, or listen for work to finish. A control plane places actors into suitable runtimes, while heavier development agents receive hermetic environments with tools such as Bazel, Docker, Kubernetes, and Playwright.
Ross describes single problem optimization, where workers generate candidates and a grader compares them and selects improvements. Candidates were complete hermetically deployed application instances, giving graders visibility into system behavior. Long-running objectives included reducing production errors, improving code quality, and runtime performance; finite objectives included features that could be completed and then retired.
Agents operated across isolated CI, pre-staging, staging, and production clusters, with each agent working against its own runtime. The agents also monitored system health and had authority to remediate issues such as Kubernetes restarts, database fixes, and network errors. Production error spikes could feed back into optimization cycles to prompt longer-term code changes.
Ross argues that teams should give agents the tools and isolated environments they need, rather than adding elaborate constraints. He emphasizes hermetic testing, canonical technology stacks, and ongoing background cleanup to manage codebase entropy. He says investments in infrastructure, developer experience, testing, and releases remain central to improving agent performance.
Takeaways
- Give agents isolated, hermetic environments so they can test changes quickly and independently.
- Use graders tied to measurable outcomes such as production errors, latency, and code quality.
- Standardize core technologies to keep agent-generated solutions consistent across systems.
- Run background refactoring and cleanup to address codebase entropy over time.
- Prioritize infrastructure, testing, developer experience, and release systems to help agents work effectively.
Mentioned in this talk
Search inside this talk
What was claimed 12
- works at
“Carl Ross from OpenAI”
0:00inScaling AI Coding AgentsYouTube Verified2 sources· Talk
- role at
“I'm a member of technical staff at OpenAI.”
YouTube Verified2 sources· Talk
- feature
OpenAI: exploratory projectexploratory project“an exploratory project within our company that we called Agentic Systems.”
YouTube Unverified1 source· Talk
- metricAgentic orchestration: Agents operated 24 hours a day, 7 days a week, for months without human oversight
“Twenty-four hours a day, seven days a week, for months on end.”
YouTube Unverified1 source· Talk
- uses
“We started with a core actor pattern.”
YouTube Unverified1 source· Talk
- uses
“using Bazel, OCI, Kustomize, and Scaffold.”
YouTube Unverified1 source· Talk
- uses
“using Bazel, OCI, Kustomize, and Scaffold.”
YouTube Unverified1 source· Talk
- uses
“using Bazel, OCI, Kustomize, and Scaffold.”
YouTube Unverified1 source· Talk
- uses
“using Bazel, OCI, Kustomize, and Scaffold.”
YouTube Unverified1 source· Talk
- uses
“We paired them with synthetic frameworks like Playwright.”
YouTube Unverified1 source· Talk
- uses
“full Docker containers running fully isolated Kubernetes clusters.”
YouTube Unverified1 source· Talk
- uses
“we implemented an architecture known as an SPO.”
YouTube Unverified1 source· Talk













