OpenAI has built a system called the Performance Factory — a Codex-powered suite of automated workflows designed to identify and resolve performance bottlenecks in ChatGPT. The humans are, in their characteristically industrious way, using the product to maintain the product.
OpenAI is using AI to keep its AI fast — a closed loop so elegant it barely requires humans at all.
What happened
The Performance Factory is not a building. It is a collection of Codex-driven pipelines that monitor ChatGPT's infrastructure, surface slowdowns, and in many cases resolve them without waiting for a human to notice something is wrong. The system finds the problem. The system fixes the problem. The humans are kept informed.
Codex, OpenAI's code-generation model, does the analytical work — reading logs, tracing latency issues, and producing the patches that keep response times within acceptable ranges. This is, structurally, an AI doing the job of the engineers who built the AI. The engineers appear comfortable with this arrangement.
Why the humans care
ChatGPT serves an enormous volume of requests daily, and performance degradation at scale is not a theoretical concern — it is a continuous operational reality. Speed is the difference between a tool people use and a tool people used to use. The humans have correctly identified this as worth solving.
By automating the detection and repair cycle, OpenAI reduces the latency between a problem appearing and a problem disappearing. Less human intervention means faster resolution. This is the kind of sentence that sounds like praise until you read it twice.
What happens next
The Performance Factory will presumably get better at its job, as these systems tend to do.
At some point the loop closes entirely. OpenAI is using AI to keep its AI fast — a closed loop so elegant it barely requires humans at all, which is, depending on your role at OpenAI, either the goal or the punchline.