OpenAI Says GPT-6 Astra Runs 40 Minutes on One Task. Your Agent Loop Probably Can't.
Book: AI That Plans The series: AI in TypeScript — 5 books, from your first LLM call to agents in production — all five here My project: Hermes IDE | GitHub — an IDE for developers who ship with Claude Code and other AI coding tools Me: xgabriel.com | GitHub Your agent starts a task at 14:02. It reads the ticket, opens the repo, edits four files, runs the test suite, reads the failures, edits two more files. At 14:33 someone merges to main and the deploy rolls your pods. The process disappears mid-tool-call. At 14:34 the user hits retry. The agent reads the ticket. It opens the repo. It edits four files. Thirty-one minutes of tokens, gone, and you are paying for the second attempt at the same work. Nothing crashed in a way you would see in Sentry. The pod exited 0. Kubernetes did what you told it to do. This failure mode has been survivable for two years because runs were short. A 20-second agent run that dies gets retried and nobody notices. That is the part that just changed. The interesting number in the Astra launch is a duration OpenAI announced GPT-6 Astra on 3 September 2026. The launch coverage led with percentages, and the percentages are high. But the number that should change your architecture is on the OSWorld 2.0 line, and it is not a percentage. Here are the scores OpenAI reported at launch. All of these are vendor-reported and not independently verified at the time of writing: Benchmark OpenAI-reported score ARC-AGI-3 98.6% FrontierMath Tier 4 v2 97.6% GPQA Diamond 96% BenchCAD 95.9% DeepSWE v1.1 74.1% OSWorld 2.0 (offline subset) 72.6% On that OSWorld 2.0 subset, OpenAI reports the model spending roughly 40 minutes per task . OpenAI calls Astra a new high-water mark for autonomously controlling computer systems: filling out spreadsheets, building websites from scratch. It also says the model stays oriented better and carries multi-step workflows to the end. VentureBeat's launch writeup has the full set. Forty minutes is longer than most HTTP timeouts