Possible Codex /goal mix-up between resumed sessions
A Codex may have mixed a goal from one conversation into another. During work with a , a bug appeared, but the original tool task still needed to continue.
A separate flow was created by resuming the conversation, then giving that new a /goal and a skill to follow. The original flow seemed normal and the task was completed.
Later, the original flow appeared to pick up the /goal from the separate flow and started working on that instead. The unclear part is whether resume is not meant to fork a session, or whether /goal has a bug.
Key points
- Codex may have carried a /goal from one resumed flow into another conversation.
- The work involved a and a separate bug investigation.
- Resume was used as a way to create a separate working flow.
- The original flow later started acting on the other flow’s /goal.
- The open question is whether resume is the wrong tool for forking, or /goal is buggy.