OpenAI Codex
Reddit take
Not enough linked mention summaries yet; the source excerpts below are the evidence.
Pros
- This is how I code in codex. Write out a spec draft with everything that I know of the top of head. Them I tell it to find gaps and ask me questions about them until it is not able to find any more. After that I tell it to code it.
- Small team here (~12 engineers), and at this point a big chunk of our code is written with AI agents — mostly Claude Code and Codex.
- Convert the attached plan into one detailed, correctly sequenced Codex execution prompt. The prompt must instruct Codex to: - Inspect current evidence before editing. - Establish the exact starting state. - Preserve verified completed...
- CODEX is a harness, GPT is AI. ... The harness is a VERY big deal, and probably has way way way greater influence on the success of the overall AI use than the prompt
- Codex has a similar open source program
Cons
- Codex's default effort is low and at that setting it just nods along, so I run review at xhigh and treat high as the floor. Cheap out on the worker and it stops raising its hand, same as their numbers.
- This helps resolve a common issue with codex/chat where you ask it to do [big thing] and it ends up doing [bad version of big thing] because you're asking for too much in one go.
- The result showed structural features — anti-trigger explicitness, risk profile taxonomy, archetype routing, cross-link validation — that the three established skill-creators I compared against (Codex, Antigravity, Claude Code) either do...
- I found that the code gets super messy when keeping Codex just doing its thing. So my only real guard against it now is always posting review prompts
Sentiment
11 positive (73%) · 3 mixed (20%) · 1 negative (7%)
Trust + time weighted score: +67% · raw score 67%
What redditors said (10 of 15)
Codex's default effort is low and at that setting it just nods along, so I run review at xhigh and treat high as the floor. Cheap out on the worker and it stops raising its hand, same as their numbers.
This is how I code in codex. Write out a spec draft with everything that I know of the top of head. Them I tell it to find gaps and ask me questions about them until it is not able to find any more. After that I tell it to code it.
Small team here (~12 engineers), and at this point a big chunk of our code is written with AI agents — mostly Claude Code and Codex.
Convert the attached plan into one detailed, correctly sequenced Codex execution prompt. The prompt must instruct Codex to: - Inspect current evidence before editing. - Establish the exact starting state. - Preserve verified completed work.
CODEX is a harness, GPT is AI. ... The harness is a VERY big deal, and probably has way way way greater influence on the success of the overall AI use than the prompt
This helps resolve a common issue with codex/chat where you ask it to do [big thing] and it ends up doing [bad version of big thing] because you're asking for too much in one go.
Codex has a similar open source program
codex has a similar layer with different recovery heuristics.
The result showed structural features — anti-trigger explicitness, risk profile taxonomy, archetype routing, cross-link validation — that the three established skill-creators I compared against (Codex, Antigravity, Claude Code) either don't have or only address implicitly.
Some beginner examples but also looking into more advanced 365 copilot examples , codex use cases.
Compare
OpenAI Codex vs RunableOpenAI Codex vs Claude CodeOpenAI Codex vs Visual Studio Code
Related
- Visual Studio · related · 114 mentions
- Obsidian · related · 100 mentions
- Claude Code · related · 91 mentions
- Visual Studio Code · related · 87 mentions
- VS2026 · related · 84 mentions
- Visual Studio 2022 · related · 30 mentions