Remote mobile session enters Plan Mode without the user selecting it

Summary

A remote Codex session is being forced into Plan Mode even though I did not select Plan Mode or add a plan tag in the ChatGPT mobile app.

The assistant repeatedly says the conversation is in Plan Mode and refuses to make the requested repository changes, despite the user asking to build/implement the already-approved plan.

Environment

• Client: ChatGPT mobile app using the remote Codex experience
• Device/OS: not captured
• App version: not captured
• Connected repository/session: remote Codex session
• Account/workspace: same account used for the remote session

Steps to reproduce

1. Open a remote Codex session from the ChatGPT mobile app.
2. Do not select Plan Mode and do not add a plan tag.
3. Ask Codex to investigate a repository task.
4. Approve or request implementation after the plan is complete.
5. Observe that Codex still reports that it is constrained to Plan Mode and will not edit files.

Expected behavior

The session should use the mode selected by the user. If no Plan Mode was selected, Codex should be able to execute an explicitly requested implementation after planning is complete.

Actual behavior

The session behaves as though a developer-level Plan Mode instruction is active. The assistant says it cannot edit files because it is still in Plan Mode, even though the mobile user never selected that mode.

Impact

Remote mobile users can become stuck in a planning-only state and cannot progress from an approved plan to implementation. The visible mobile mode and the mode enforced by the session may be out of sync.

Request

Please investigate remote mobile session-state synchronization and ensure that Plan Mode is only active when selected or explicitly required by the session configuration. If a higher-priority configuration forces Plan Mode, expose that state clearly in the mobile UI so the user can understand why execution is blocked.

Start with the remote mobile session-state synchronization entry point described in the report and reproduce the listed steps without selecting Plan Mode. Compare the mobile-selected mode with the mode enforced by the remote session; done means an explicitly requested implementation can proceed, or any higher-priority Plan Mode requirement is shown clearly in the mobile UI.