Home / Companies / OpenAI / Blog / Post Details
Content Deep Dive

Maintaining software with the GPT-6 family

Blog post from OpenAI

Post Details
Company
Date Published
Author
Rodrigo Roim
Word Count
1,911
Company Posts That Month
1
Language
English
Hacker News Points
-
Post removed?
No
Summary

OpenAI’s Core Experimentation team describes using Codex-based GPT-6 models to automate software maintenance tasks while retaining human review and validation. GPT-6 Astra was used to investigate and remove dead code by examining repositories, pull requests, internal discussions, production profiling, and feature-flag systems, contributing to more than 1,400 merged maintenance pull requests and over 800,000 deleted lines of code, alongside smaller container images and reduced test-suite complexity. The team also applied the models to identify stale Statsig experiments and flags, including costly configurations that static analysis had missed, with one reviewed removal estimated to save 0.42% CPU in a major service. In a comparison across more than 6,000 files, GPT-6.1 Sol Ultra found nearly as many stale-experiment issues as Astra Ultra at a fraction of the API cost, although it missed some dependency-related flags, illustrating the importance of prompt refinement and repeated evaluation as models evolve. Additional uses included fixing flaky tests, improving agent instructions, and optimizing CI, with reported reductions in median CI completion time from about 10 to 4.5 minutes. The team recommends beginning with small, evidence-based draft changes, measuring results, incorporating reviewer feedback into prompts, and gradually expanding successful workflows across larger codebases.

Trends Found in this Post
Trend Post Mentions Total Month Mentions Posts Companies MoM
GPT-6.1 Sol 16 168 25 13 +1427%
GPT-6 Astra 12 167 38 24 -73%
Harness engineering 1 74 45 26 -54%
Subagents 1 120 42 26 -54%
Use This Data

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.