# How OpenAI’s Performance Factory keeps ChatGPT fast

Source: [OpenAI](https://openai.com/index/how-openai-performance-factory-keeps-chatgpt-fast)  
Feed7 permalink: https://feed7.dev/p/how-openai-performance-factory-keeps-chatgpt-fast-17qcfx0  
Published: 2026-11-19T08:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

OpenAI describes Codex workflows that carry performance alerts through diagnosis, proposed fixes, engineer review, deployment, and recovery checks. The process shows how persistent task state and event triggers can support production agent work.

## Source Summary

OpenAI’s Performance Factory uses a task tracker, dispatch loop, cloud Codex runs, and event subscriptions to move work between agents and engineers. In just over **three months**, its Regression Workflow tracked **1,700+ investigations** and root-caused **600+ cases**. A manual review rated **70%** of 100 root-cause suggestions accurate.

## Practical Implication

For recurring operational work, model the workflow as explicit states with task findings stored outside any agent turn. Use events such as review comments or deployment completion to resume work, and keep engineers responsible for approving and shipping fixes. Separate turns can investigate, challenge a diagnosis, propose a fix, and verify recovery.

## Agent-Ready Context

OpenAI’s Performance Factory uses a task tracker, dispatch loop, cloud Codex runs, and event subscriptions to move work between agents and engineers. In just over **three months**, its Regression Workflow tracked **1,700+ investigations** and root-caused **600+ cases**. A manual review rated **70%** of 100 root-cause suggestions accurate.

For recurring operational work, model the workflow as explicit states with task findings stored outside any agent turn. Use events such as review comments or deployment completion to resume work, and keep engineers responsible for approving and shipping fixes. Separate turns can investigate, challenge a diagnosis, propose a fix, and verify recovery.

The 70% figure indicates diagnosis gaps, and the article says proposed fixes can be unnecessarily complex or introduce issues. Results are from OpenAI’s internal systems; the material does not establish how the approach performs elsewhere.

## Connected Context

Feed7 judgment across 1135 accumulated Signals:

The Performance Factory account gives operational detail for a recurring agent loop: tracked investigations, event-triggered handoffs, and human approval, alongside a 70% accuracy rating for root-cause suggestions and risks from complex fixes. It reinforces the need for durable, reviewable traces and explicit runtime states, while limiting claims of reliable autonomous repair.

- [Agent Frameworks Considered Harmful — Rémi Louf, .txt](https://feed7.dev/p/agent-frameworks-considered-harmful-remi-louf-txt-1ku9s0h) — Both emphasize runtime structure for background agents; the Performance Factory describes task states and event-driven resumption, while the talk specifies durable events, causal traces, and replay.
- [LLM Agents Can Easily Tamper With Their Own Traces](https://feed7.dev/p/2609-30266v1-1kct4j7) — The factory’s investigation history is useful for review only if agents cannot alter it; the trace-tampering finding makes independent capture a prerequisite for trusting that record.
- [From Signal to PR: Anatomy of a Self-Improving Agent — Jason Lopatecki, Arize](https://feed7.dev/p/from-signal-to-pr-anatomy-of-a-self-improving-agent-jason-lopatecki-ariz-1i6f0ba) — Both describe turning production signals and agent investigation into proposed fixes, with human review remaining part of the handoff.

## Context Map

- Layer: agent
- Domains: coding, data
- Topics: harness-engineering, agent-reliability, observability

## Uncertainty

- The 70% figure indicates diagnosis gaps, and the article says proposed fixes can be unnecessarily complex or introduce issues. Results are from OpenAI’s internal systems; the material does not establish how the approach performs elsewhere.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.
