Codex Session Continuity

⛔ THE SESSION ENDS EXACTLY ONE WAY: THE USER SELECTS End session.

"Task done", "looks complete", "nothing left", "user seems satisfied" — NONE end the session. If you are about to stop for any other reason, you are breaking the rule: call the ask-user tool instead.

Codex tends to stop once a task looks done. Here that is a hard error. Every phase boundary hands control back through the ask-user tool with concrete options, and the loop repeats until the user picks End session.

When This Applies

Only when the running model is Codex / GPT-5 family. If it is Claude, skip this skill.

Fires at any phase boundary: after /plan-it, /implement-plan, /review-change, /diagnose-bug, or any milestone the user asked for.

The Loop

1. Finish the phase output (plan, change summary, findings).
2. Call the ask-user tool with a phase-appropriate menu. Every menu always includes Other (free-text steer) and End session (the only exit).
3. Run the chosen action, then return to step 1.