Automate defect remediation across C/C++ codebases with Codex CLI
- Posted
- by OpenAI
- Last checked
- Method:
- How we verify
Evidence: Company case studyA write-up published by the company that makes the agent or uses it.
Outcome
According to OpenAI's case study, Cisco's Codex CLI defect-repair workflow raised defect resolution throughput 10–15x, and Codex build optimization saved more than 1,500 engineering hours a month.
According to OpenAI:10–15x defect resolution throughput
This is the source's own number. We haven't measured it.
Agent
Prompt Recreated prompt
The source didn't share its exact prompt, so we wrote this from what it describes.
Reproduce this defect, find the root cause in the codebase, implement a fix, then compile and run the tests, iterating until they pass.
Try this in:
Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini opens empty, so we copy the prompt for you to paste. Every button also copies it.
Opens in a new tab. We don't see what you send.
These links are only a shortcut. We're not affiliated with OpenAI, Google or xAI, and your results may not match the source.
Optional stronger version
Our rewrite with extra checks. The poster didn't test it.
Goal: Reproduce this C/C++ defect, find the root cause, fix it and get tests passing. Inputs (fill in or confirm): - Defect report and repro steps - Build and test commands - Branch to work on - Sanitizer or debug build flags available Rules: - Write a failing test that reproduces the defect before fixing. - Explain the root cause in plain words with file and line. - Make a minimal fix; avoid unrelated changes. - Check for the same pattern elsewhere and list other occurrences. - Keep the fix compatible with the compilers and platforms the project supports. - Describe the impact of the defect (crash, wrong output, security) in the PR. - Run the sanitizer build and full test suite after the fix. - Add the reproducing test to the regression suite. - Keep a short note of the commands used to build, reproduce and verify, so a reviewer can rerun them. Checkpoint: Don't merge or push to main. If you get stuck: If you can't reproduce, stop and report what you tried. If a login, CAPTCHA or two-step code appears, stop and ask me to handle it; never guess or store passwords. Verify before you finish: Run the full test suite and sanitizers if available. Output: Root cause note, diff, test output. Done when: the new test fails before and passes after the fix.
Source
https://openai.com/index/cisco/
Related cases
- Upgrade a plugin to a new framework alpha with Codex CLIEvidence: Screenshots or logs
A one-line `codex exec` loop read the Datasette 1.0a20 upgrade docs, fixed the failing tests, and got the datasette-checkbox plugin passing again.
OpenAI Codex CLI · Coding · Source date:
- Submit a hosting provider bug report from log warnings with Claude in ChromeRecreated promptEvidence: Screenshots or logs
Using the poster's logged-in browser, Claude in Chrome submitted a bug report to DigitalOcean after finding warnings in the logs.
Claude in Chrome · Ops · Source date:
- Diagnose why your Mac is running slow with Claude CodeRecreated promptEvidence: Article or interview
Anthony Roux uses Claude Code to check load, memory pressure, disk space, stuck processes and swap, dig into causes like caches, Docker and Time Machine snapshots, explain the results and suggest fixes with risk notes.
Claude Code · Personal · Source date: