Slash command fuzzy search not working correctly in latest codex-cli release

Resolved 💬 4 comments Opened Dec 11, 2025 by tianweilong Closed Dec 11, 2025
💡 Likely answer: A maintainer (etraut-openai, contributor) responded on this thread — see the highlighted reply below.

What version of Codex is running?

0.69

What subscription do you have?

PRO

Which model were you using?

gpt-5.1-codex-max

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

After updating to the latest version of codex-cli, the fuzzy search behavior for slash commands seems to be broken. Some commands that should match the typed pattern are not shown in the suggestion list, and the results appear inconsistent.

For example:

Typing /a correctly shows /approvals, /compact, /feedback, etc.

Typing /ac unexpectedly returns no results, even though commands like /feedback, and /compact contain the substring "ac" and used to match in previous versions.

There is no visible error message—only the autocomplete results are missing or inconsistent.

This behavior suggests that the fuzzy-matching logic may have regressed in the latest release.

<img width="304" height="243" alt="Image" src="https://github.com/user-attachments/assets/ffb55542-f46f-44ba-91ee-ecc58783dadf" />

<img width="315" height="243" alt="Image" src="https://github.com/user-attachments/assets/871b0a48-56fb-48e9-aa27-ccd2df9cf89a" />

What steps can reproduce the bug?

Install or update to the latest version of codex-cli.

Open the CLI and start entering a slash command.

Type /a and observe that several matching commands appear (e.g., /approvals, /compact, /feedback).

Then type /ac — expected behavior is that commands containing "ac" should appear, but no suggestions are shown.

Repeat with other partial substrings and note irregular or missing fuzzy-match results.

What is the expected behavior?

_No response_

Additional information

_No response_

View original on GitHub ↗

4 Comments

etraut-openai contributor · 8 months ago

@448523760, I think your PR introduced this regression.

448523760 contributor · 8 months ago

I will double check that part

448523760 contributor · 8 months ago
@448523760, I think your PR introduced this regression.

Yes, i just using the prefix check. And I see you already make the change that using the fuzzy_match.

etraut-openai contributor · 8 months ago

@tianweilong, thanks for the bug report. This will be fixed in the next release.