What version of Codex is running?
Codex Windows Desktop package: OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0
Codex Desktop file/product version: 148.0.7778.179
Bundled/current CLI observed from Desktop runtime: codex-cli 0.136.0-alpha.2
What platform is your computer?
Windows 11 x64, build 10.0.26200
What issue are you seeing?
In Codex Windows Desktop, typing /goal in the composer opens the slash-command picker but it shows No commands / `鏃犲懡浠.
This appears to contradict the current Codex documentation and changelog:
- The Codex app commands documentation lists
/goal as an available slash command.
- The same documentation says that if
/goal does not appear, users should enable:
- The Codex changelog says Goal mode is no longer experimental and is available in the Codex app, IDE extension, and CLI.
- The Windows documentation / launch notes say the Codex app is available on Windows.
On this machine, the local config and CLI-side feature state are already correct:
%USERPROFILE%\.codex\config.toml contains:
codex features list reports:
The Desktop goal API also appears to exist and partially work:
- Desktop logs show goal API calls such as:
method=thread/goal/get
method=thread/goal/set
- The UI exposes a message action equivalent to "Set as goal" (
璁剧疆鐩爣), and using that path can call thread/goal/set.
So this does not look like Goal mode is unavailable. It looks like the Windows Desktop slash-command list / renderer-side feature gate does not include goals, or does not register /goal, even when features.goals = true is effective for the CLI/app-server side.
What steps can reproduce the bug?
- On Windows, install/run Codex Desktop.
- Enable goals in
%USERPROFILE%\.codex\config.toml:
- Confirm
codex features list shows goals stable true.
- Fully quit/restart Codex Desktop.
- Open any local thread.
- Type
/goal in the composer.
Actual behavior
The slash-command picker shows No commands / 鏃犲懡浠; /goal` is not available from autocomplete.
Expected behavior
The Windows Desktop composer should show /goal as a slash command, matching the current Codex docs and changelog. It should allow users to set/view/manage a goal from the slash-command surface.
If Windows Desktop intentionally supports goals only through the message action / goal UI, the docs should say that explicitly. But the current docs say /goal is available in the app composer and that enabling features.goals should make it appear.
Additional diagnostics
Clearing Desktop web cache directories and restarting did not change the behavior.
Desktop logs after restart show enabledFeatures entries that include thread_tools, apps, plugins, tool_suggest, etc., but do not include goals, while the same logs still record thread/goal/get calls. Older logs also record successful thread/goal/set calls from the message-action path.
The installed app.asar also contains goal-related strings/events such as /goal, thread/goal/get, and thread/goal/set, so this looks more like a command registration or feature propagation issue than a missing binary capability.
Related issues:
What version of Codex is running?
Codex Windows Desktop package:
OpenAI.Codex_26.527.7698.0_x64__2p2nqsd0c76g0Codex Desktop file/product version:
148.0.7778.179Bundled/current CLI observed from Desktop runtime:
codex-cli 0.136.0-alpha.2What platform is your computer?
Windows 11 x64, build
10.0.26200What issue are you seeing?
In Codex Windows Desktop, typing
/goalin the composer opens the slash-command picker but it showsNo commands/ `鏃犲懡浠.This appears to contradict the current Codex documentation and changelog:
/goalas an available slash command./goaldoes not appear, users should enable:On this machine, the local config and CLI-side feature state are already correct:
%USERPROFILE%\.codex\config.tomlcontains:codex features listreports:The Desktop goal API also appears to exist and partially work:
璁剧疆鐩爣), and using that path can callthread/goal/set.So this does not look like Goal mode is unavailable. It looks like the Windows Desktop slash-command list / renderer-side feature gate does not include
goals, or does not register/goal, even whenfeatures.goals = trueis effective for the CLI/app-server side.What steps can reproduce the bug?
%USERPROFILE%\.codex\config.toml:codex features listshowsgoals stable true./goalin the composer.Actual behavior
The slash-command picker shows
No commands/鏃犲懡浠;/goal` is not available from autocomplete.Expected behavior
The Windows Desktop composer should show
/goalas a slash command, matching the current Codex docs and changelog. It should allow users to set/view/manage a goal from the slash-command surface.If Windows Desktop intentionally supports goals only through the message action / goal UI, the docs should say that explicitly. But the current docs say
/goalis available in the app composer and that enablingfeatures.goalsshould make it appear.Additional diagnostics
Clearing Desktop web cache directories and restarting did not change the behavior.
Desktop logs after restart show
enabledFeaturesentries that includethread_tools,apps,plugins,tool_suggest, etc., but do not includegoals, while the same logs still recordthread/goal/getcalls. Older logs also record successfulthread/goal/setcalls from the message-action path.The installed
app.asaralso contains goal-related strings/events such as/goal,thread/goal/get, andthread/goal/set, so this looks more like a command registration or feature propagation issue than a missing binary capability.Related issues:
/goalmissing /No commandseven though Goal mode is GA. This Windows report appears to be the same class of bug, still reproducible onOpenAI.Codex_26.527.7698.0./goalsupport for the Windows app. This report is narrower: the current Windows app appears to have goal API/UI action support, while the/goalslash command remains missing./goalignores auto-createdPasted text.txtattachments and treats the goal as empty #25346 is a Windows Desktop/goalbehavior bug after/goalis present/used with pasted-text attachments; this report is about slash-command registration/visibility before/goalcan be invoked.