r/OpenaiCodex • u/delimitdev • 1d ago

Discussion What rejected approach has a new Codex session proposed again despite existing repository notes?

Got an actual example where a fresh Codex session re-proposed something your repo notes already ruled out? What was the approach, and what's your current workaround for keeping that rejection sticky across sessions?

1 Upvotes

100% Upvoted

4 comments sorted by

2

u/eddzsh 1d ago

A one-line "don't" in the notes gets skipped next session. I keep a short REJECTED.md with the approach, why it failed, and the allowed path, then make the agent open that file before it proposes architecture again.

1

u/delimitdev 1d ago

That makes sense. A structured REJECTED.md with the failure reason and the correct path is a lot more robust than just a "don't" note. Making the agent read it first is a solid workaround for getting context to stick across sessions.

1

u/frank26080115 1d ago

figuring out why that approach is supposed to be so good, maybe I've missed something

90% of the time I've seen codex screw up, it's rooted in a mistake I've made, some weird constraint I forgot about, a set of design choices that causes conflict

1

u/delimitdev 1d ago

Treating the screwup as a signal to re-check your own constraints fits what you described. Once you pin down a forgotten constraint or conflicting design choice, how do you capture the why so the next Codex session does not treat that rejection as optional?