codex - 💡(How to fix) Fix codex-cli 0.128.0 on WSL/Linux reports "Unrecognized command '/goal'" although v0.128.0 release notes mention /goal [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#20548Fetched 2026-05-01 05:41:53
View on GitHub
Comments
1
Participants
2
Timeline
6
Reactions
0
Timeline (top)
labeled ×4closed ×1commented ×1

Root Cause

This may be specific to the linux x64 npm package, because issue #20536 reports that a Windows / PowerShell install of codex-cli 0.128.0 does contain goal-related strings such as:

RAW_BUFFERClick to expand / collapse

What version of Codex CLI is running?

codex-cli 0.128.0

What subscription do you have?

ChatGPT Pro

Which model were you using?

gpt-5.5

What platform is your computer?

Windows 11 with WSL2 Ubuntu

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

Windows Terminal with WSL2 Ubuntu shell

What issue are you seeing?

I installed/reinstalled codex-cli 0.128.0, but the new /goal slash command is not recognized in the TUI.

When I type /goal test, Codex shows:

Unrecognized command '/goal'. Type "/" for a list of supported commands.

This seems inconsistent with the v0.128.0 release notes, which mention persisted /goal workflows and TUI controls for create / pause / resume / clear.

I also checked the installed binary with strings, but it does not appear to contain any goal-related strings.

What steps can reproduce the bug?

  1. Install codex-cli 0.128.0 on WSL2 Ubuntu:

    npm uninstall -g @openai/codex npm install -g @openai/[email protected]

  2. Confirm the version:

    codex --version

    Output:

    codex-cli 0.128.0

  3. Start Codex TUI:

    codex

  4. Type:

    /goal test

  5. Observe that the TUI shows:

    Unrecognized command '/goal'. Type "/" for a list of supported commands.

  6. Check whether the installed binary contains goal-related strings:

    strings "$(readlink -f "$(which codex)")" | grep -i "goal" | head -50

    Output is empty.

What is the expected behavior?

No response

Additional information

I am running this on WSL2 Ubuntu / linux x64.

The v0.128.0 release notes mention persisted /goal workflows, App Server APIs, model tools, runtime continuation, and TUI controls for create / pause / resume / clear.

However, on my WSL/Linux install, /goal is not recognized by the TUI, and the installed binary does not appear to contain goal-related strings.

This may be specific to the linux x64 npm package, because issue #20536 reports that a Windows / PowerShell install of codex-cli 0.128.0 does contain goal-related strings such as:

  • Usage: /goal <objective>
  • /goal pause
  • /goal resume
  • /goal clear

Diagnostics I can provide:

codex --version which -a codex readlink -f "$(which codex)" npm root -g npm ls -g @openai/codex --depth=0 strings "$(readlink -f "$(which codex)")" | grep -i "goal" | head -50

extent analysis

TL;DR

The /goal command is not recognized in the Codex TUI, possibly due to a missing or incomplete implementation in the Linux x64 npm package of codex-cli 0.128.0.

Guidance

  • Verify that the issue is specific to the Linux x64 npm package by comparing the behavior with a Windows or other platform installation.
  • Check the release notes and documentation for any platform-specific limitations or requirements for the /goal command.
  • Investigate issue #20536 for potential clues or workarounds, as it reports similar behavior on Windows/PowerShell.
  • Consider reaching out to the Codex development team or community for further assistance, as this may be a bug or missing feature in the Linux x64 package.

Notes

The issue seems to be specific to the Linux x64 npm package, and the presence of goal-related strings in the Windows/PowerShell installation suggests a potential platform-specific difference.

Recommendation

Apply workaround: Try installing codex-cli on a different platform, such as Windows, to see if the /goal command is recognized, and report the findings to the development team for further investigation.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING