Codex-maxxing
dnw
24 points
13 comments
May 19, 2026
Related Discussions
Found 5 related stories in 84.1ms across 8,303 title embeddings via pgvector HNSW
- How Codex Is Built tosh · 18 pts · March 08, 2026 · 63% similar
- Codex for almost everything mikeevans · 786 pts · April 16, 2026 · 62% similar
- Codex Plugins epaga · 13 pts · March 27, 2026 · 58% similar
- Why Codex works better than Claude Code for my production monolith anophelon · 14 pts · April 29, 2026 · 55% similar
- Codex is now in the ChatGPT mobile app mikeevans · 275 pts · May 14, 2026 · 55% similar
Discussion Highlights (6 comments)
armada1122
The diff-as-review point is the one I keep coming back to. The cost of memory-as-files isn't writing them. It's that the agent will cheerfully claim it updated something and not actually do it, or write a one-line stub that satisfies the spec but loses the original signal. Without a verification layer, the vault accumulates plausible-looking entries that quietly drift from reality. What ended up working for me was treating the agent's self-reported summary as a wish, not a fact. A separate process diffs the actual file system against the claimed changes and flags mismatches. After a few cycles, the agent gets calibrated and stops claiming things that don't survive a file check. That has the side benefit of making the diff review itself much higher signal: most of what shows up is real. The split I'd make early is per-agent instructions vs. cross-thread shared notes. They sound like the same artifact, but “what this agent should always do” and “what sibling work just learned” age very differently. Mixing them means the wisdom gets stale together.
parf02
Most people I know underutilize voice mode. Such a game changer for making brain dumps the LLM can just gobble up
mohsen1
in tsz ( https://tsz.dev ) I am Codex-Maxxing with this: Give each Codex an AgentName and ask them to mark their PR/issue/comments with those. Have one or two "managers" that manage PRs and overall project direction. I write the project directions and make long lasting issues. Each Codex session has an almost unachievable `/goal` but they are asked to achieve the goal by landing changes in `main` via PRs I am running about 14 Codex sessions on 4 machines right now for about two weeks since OpenAI 10x'ed my 20x account and I simply can not run out of tokens fast enough. Side note: I have multiple Claude accounts too but the new Claude Code `/goal` command is seriously broken. It waits long pauses between iterations and sometimes prematurely stops.
esperent
> Every 30 minutes, check Slack and Gmail for unanswered messages that need my attention... > When I come back to Slack, replies are often already sitting in drafts. I still decide what gets sent, but the expensive part of gathering context is done. This just feels so dystopian to me. I hope that I never work with you or someone else doing this. I personally do use LLMs for work messaging but I'm extremely careful to state clearly like "here's a draft for that quotation request that Claude wrote:" or something like that. I would never present that as my own words.
4k0hz
The author of this post works at OpenAI on the Codex team.
grebc
All the AI stuff lately is just like Unix Porn reddit but posted to places where the people don’t care about it.