TL;DRSame person, same model — different usage, wildly different results. The dividing line in the official best practices: configure it like a teammate, or use it like a vending machine. Here's the three-piece teammate setup and how to migrate over.
Sources SOURCES
Distilled from public community discussions. This page only breaks them down and verifies — it never reposts the original; opinions belong to their authors.
Facts FACTS
Check these claims against the listed sources. For allowance mechanics, first-party account displays outrank community summaries.
- The official best-practice advice is blunt: treat Codex as a teammate that needs configuring, not a one-off Q&A machine — the one line in the guide that changes how everything else in it reads.
- The companion move is persisting long-lived instructions into AGENTS.md, so the constraints stay effective across sessions — the file is where teammate memory lives.
- The recommended workflow also includes plan-first execution and full context up front — the teammate mode's other two pillars.
- The r/codex field post shows what maintaining AGENTS.md as a long-term asset looks like in practice — static repo analysis plus layered context, maintained the way you'd maintain any other long-lived asset.
Concepts CONCEPTS
Not everything said in a community thread is a fact — each concept carries its nature label. Read the label first.
The official best-practices framing: invest in configuration continuously — context, conventions, permissions, workflow — the way you would with a new colleague, instead of re-briefing from zero every session. Teammates get onboarding, standing conventions, and gradually earned trust; the configuration is that process.
The anti-pattern the official guidance names: brief everything from scratch each session, then watch the same class of error recur in the next one. Every session pays the onboarding cost again and banks none of it.
A summary of community practice: every correction written back into config improves the agent's output over time. The direction is widely reported; the size of the "compounding" has no public measurement.
A popular mental model: AGENTS.md is the onboarding doc, plan-first is the reporting routine, approval tiers are the badge access. It's a thinking tool, not a spec — the analogy breaks where agents don't ask questions on their own, and a human has to cover that gap.
Takeaways TAKEAWAYS
Q&A mode looks cheaper, but the cost hides in the repetition: every session re-briefs the repo structure, the commands, and the no-go zones; the same class of error keeps coming back; the variance in results runs wide. The machine never learns your repo — the teammate does, and that's the entire difference in outcomes. The official best practices say it plainly: don't treat Codex as a one-off Q&A machine, treat it as a teammate that needs configuring. Every un-briefed session is that cost compounding in the wrong direction.
Teammate mode unpacks into three pieces. Instruction persistence: long-lived constraints go into AGENTS.md and stay effective across sessions. Workflow locks: plan before code, full context up front — these official recommendations are themselves workflows you can encode as standing conventions. Stable tiers: sandbox and approval defaults, set once, not re-adjusted on the fly. All three are configure-once, benefit-forever assets, and none of them is exotic — the discipline is running all three at once, on every task. Skip one and you're back to negotiating with the agent instead of working with it.
Migration doesn't require a rewrite. Start with your next real task: wherever it went wrong, write the matching constraint back into config; whatever you catch yourself re-explaining, write that in too. The people maintaining AGENTS.md as a long-term asset — like that public field file on r/codex — took exactly this road — no migration project, no retraining, just write-backs that accumulate. A month later, look at the diff on your config file: if it grew, the collaboration is working; if it didn't move, you're still in Q&A mode with extra steps. The file's diff is the receipt.
Keep reading NEXT
Want today's verdict? Back to the live radar.