codex - 💡(How to fix) Fix TUI slash popup opens for fuzzy-only input but shows no matches [1 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#21398Fetched 2026-05-07 03:40:40
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×3unlabeled ×1

The TUI slash-command popup can open for fuzzy-only input even though the popup itself now filters commands by exact/prefix match only.

For example, /ac is a fuzzy subsequence match for commands like compact, so looks_like_slash_prefix opens the command popup. The popup's filtered() method then applies exact/prefix filtering and returns no items, leaving a visible popup with no matches.

This is not a request to restore fuzzy slash-command matching. The change keeps the prefix-only behavior consistent and prevents opening an empty popup for inputs that the popup cannot display.

Root Cause

The stacked branch includes #21394 because current origin/main does not compile codex-tui with Cargo without that missing AddToHistory fix.

Fix Action

Fix / Workaround

Patch

Code Example

cargo test -p codex-tui builtin_prefix_matching_is_prefix_only
cargo test -p codex-tui slash_popup_activated_for_bare_slash_and_valid_prefixes
cargo fmt --check
git diff --check
RAW_BUFFERClick to expand / collapse

Summary

The TUI slash-command popup can open for fuzzy-only input even though the popup itself now filters commands by exact/prefix match only.

For example, /ac is a fuzzy subsequence match for commands like compact, so looks_like_slash_prefix opens the command popup. The popup's filtered() method then applies exact/prefix filtering and returns no items, leaving a visible popup with no matches.

This is not a request to restore fuzzy slash-command matching. The change keeps the prefix-only behavior consistent and prevents opening an empty popup for inputs that the popup cannot display.

Reproduction

  1. Start the TUI.
  2. Type /ac in the composer.
  3. Observe that the command popup opens but shows no matches.

Patch

Slash-popup-specific diff, stacked on the compile fix from #21394:

https://github.com/misrtjakub/codex/compare/fix/tui-add-to-history-command...fix/tui-slash-popup-prefix-only-stacked?expand=1

Stacked branch against upstream main:

https://github.com/openai/codex/compare/main...misrtjakub:fix/tui-slash-popup-prefix-only-stacked?expand=1

The stacked branch includes #21394 because current origin/main does not compile codex-tui with Cargo without that missing AddToHistory fix.

Validation

cargo test -p codex-tui builtin_prefix_matching_is_prefix_only
cargo test -p codex-tui slash_popup_activated_for_bare_slash_and_valid_prefixes
cargo fmt --check
git diff --check

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

codex - 💡(How to fix) Fix TUI slash popup opens for fuzzy-only input but shows no matches [1 participants]