codex - 💡(How to fix) Fix Bring /goal support to the Codex Windows app and make goals resumable from mobile

Summary

The /goal workflow appears to be available in the Codex CLI, but not in the Codex Windows desktop app. This creates an inconsistent experience between Codex surfaces.

The Windows app should support goal-based workflows directly, and goals should be resumable from mobile, especially for long-running tasks on remote or always-on hosts.

Problem

Goal-based work is especially useful when the user wants Codex to pursue a larger outcome across multiple steps, checks, edits, and follow-ups. However, if /goal is only available in the CLI, users of the Windows app cannot use the same workflow from the main desktop experience.

This is particularly limiting when:

1. A task is too large for a single prompt-response loop.
2. The user wants Codex to keep track of the desired outcome over time.
3. The task involves remote SSH projects or long-running checks.
4. The user needs to leave the desktop and continue from mobile.
5. The desktop may be turned off while a remote host remains online.

Feature request

Add /goal support to the Codex Windows app, and allow goals to be started, resumed, monitored, and followed up from mobile.

Suggested design

• Add /goal or an equivalent goal-setting UI to the Windows app.
• Show active goals in the conversation or project sidebar.
• Let users pause, resume, cancel, or refine a goal.
• Allow a goal to survive app restarts where possible.
• Allow mobile to continue an existing goal conversation.
• If a remote or headless host mode exists, allow goals to continue on that host without requiring the Windows desktop app to stay online.
• Clearly show current goal status: planning, editing, waiting for approval, running checks, blocked, completed, or paused.
• Preserve existing approval and permission boundaries for commands, file edits, and external actions.

Mobile continuation

A user should be able to start a goal on desktop, leave the machine, and later continue from mobile by approving commands, answering questions, reviewing diffs, or redirecting the task.

Ideally, mobile should also be able to start a new goal directly on an available remote host or registered Codex environment.

Expected benefit

This would make Codex more consistent across CLI, desktop, and mobile. It would also make long-running work much easier to manage, especially for users who rely on remote development environments and need to follow up away from their desktop.

Suggested labels, if available: enhancement, app, windows, mobile, goal, cli-parity

Redaction check

This request intentionally avoids real hostnames, project names, private repositories, company names, credentials, tokens, usernames, or internal paths.