/goal auto-runs after `codex resume` without user confirmation

[trungdev05]

What version of Codex CLI is running?

codex-cli 0.128.0

What subscription do you have?

Plus

Which model were you using?

gpt-5.5

What platform is your computer?

Linux 7.0.0-14-generic x86_64 unknown

What terminal emulator and version are you using (if applicable)?

Ghostty

What issue are you seeing?

There seems to be an issue with the /goal feature when resuming an existing Codex session.

If a user enables and uses /goal, then closes the session before the goal has fully completed, running codex resume later reopens the session and automatically continues/runs the goal without asking for user confirmation.

In some cases, the goal starts running before a clear loading/status indicator is shown, so the user may not realize that Codex has already resumed execution.

What steps can reproduce the bug?

1. Start Codex CLI.
2. Enable or use the /goal feature.
3. Begin a goal-driven task.
4. Close the session before the goal is fully completed.
5. Later, run codex resume to reopen the previous session.
6. Observe that Codex automatically resumes/runs the goal.

What is the expected behavior?

When resuming a session that has an unfinished /goal, Codex should not automatically continue executing the goal.

Additional information

This can be surprising and potentially unsafe because the user may only intend to inspect the previous session, not continue executing actions automatically.

A resumed session should require explicit user consent before continuing an unfinished /goal.

[etraut-openai]

Thanks for the feedback. I had thought that users would want auto-resume, but I've received this same feedback from multiple people already. I've decided to change it to not auto-resume the goal when you resume the session. Instead, you'll need to manually resume using /goal resume. This change will be included in the next release.