Tab completion for slash commands doesn't move cursor to end of completed text
Resolved 💬 0 comments Opened Aug 18, 2025 by mkusaka Closed Aug 19, 2025
What version of Codex is running?
codex-cli 0.22.0
Which model were you using?
gpt-5
What platform is your computer?
Darwin 24.6.0 arm64 arm
What steps can reproduce the bug?
- Start codex
- Type
/c(cursor is right after the 'c') - Press Tab key to complete to
/compact(which appears as the filtered candidate) - The text
/compactis inserted, but the cursor remains at position 2 (after/c) instead of moving to the end of the completed text
What is the expected behavior?
When tab completion inserts /compact, the cursor should move to the end of the completed text (position 8, after /compact).
What do you see instead?
The text /compact is correctly inserted, but the cursor stays at position 2 (after /c), making it difficult to continue typing. Users need to manually move the cursor to the end to continue input.
Additional information
_No response_