Repository navigation
/exit and /quit slash commands missing in autocomplete (v1.14.42) #26549
Description
Description
Slash commands /exit, /quit, and /q no longer appear in the autocomplete dropdown when typing /.
- They do appear in the command palette (Ctrl+P)
- They do not appear when typing
/in the prompt
The command app.exit with slash: { name: "exit", aliases: ["quit", "q"] } is registered in app.tsx, and shows up in Ctrl+P as "Exit the app", but typing /exit or /quit in the prompt does not trigger autocomplete.
Version
OpenCode 1.14.42
Steps to reproduce
- Open OpenCode
- Type
/in the prompt - Expected:
/exitappears in the autocomplete dropdown (along with other slash commands) - Actual: No
/exit,/quit, or/qin the dropdown
Workaround
- Ctrl+P → type "exit" → select "Exit the app" → works
- Ctrl+C / Ctrl+D → exit the app
Suspected cause
The v1.14.42 changelog mentions:
Simplified TUI keybinding config into a flat keybind format.
This refactor likely broke the slash command registration in the autocomplete. The app.exit command has the correct slash metadata in app.tsx, but the autocomplete's commands() function (which reads from command.slashes()) may no longer be picking it up correctly.
References
- PR feat: tui: Port /exit command and all command aliases #3665 originally added
/exitwith aliases/quitand/q - Slash commands show correctly in Ctrl+P command palette
- Issue OpenTUI:
/quitor/exitcommands missing in 1.0.x #3679 was a previous similar report (fixed by feat: tui: Port /exit command and all command aliases #3665)
Reacted by Drevil5656, YuntianZhao, kotanys, ArtZabAZ, Gregor Dietrich, Denis, jaxver, Aaron Feledy, Mario, Vladimir Goshev and 12 more
Metadata
Metadata
Assignees
Labels
No labels
Activity
github-actions commentedon May 9, 2026
This issue might be a duplicate of (or regression from) a previously fixed issue. Please check:
/quitor/exitcommands missing in 1.0.x #3679: Same symptom —/quitor/exitcommands missing in slash command autocomplete (was fixed by PR feat: tui: Port /exit command and all command aliases #3665, appears to have regressed in v1.14.42)AaronFeledy commentedon May 9, 2026
Same on v1.14.43
mattisking commentedon May 9, 2026
Same on 1.14.4
kagura-chen commentedon May 10, 2026
I've identified the root cause: the
app.exitcommand has anenabledfunction that returnsfalsewhen the prompt has input, but the slash autocomplete list is built from entries filtered byvisibility: "reachable", which excludes disabled commands. So typing/(non-empty input) hides/exitfrom the dropdown. Working on a fix.jackusay commentedon May 10, 2026
Same on 1.14.46
hugalafutro commentedon May 10, 2026
not a single slash command works for me in 1.14.46 /models /status nothing - i can mash enter for a minute and then suddenly it will open
CasualDeveloper commentedon May 10, 2026
Experiencing
/exitmissing too on a local build based onb8ca71d309(0.0.0-b8ca71d309-casual-202605100320).I left an implementation note on the linked fix PR (#26606); keeping the technical discussion there.
P.S. @hugalafutro For me,
/modelsand/statusstill appear and work. (Update:/compacttoo)XiaoPengYouCode commentedon May 10, 2026
Still reproducible in v1.14.46. PR #26606 looks like the right fix — would be great to get it reviewed and merged.
hugalafutro commentedon May 10, 2026
@CasualDeveloper it's not that they don't appear, the list activates, but I cannot activate any of the commands I can press enter on any command in the list and the list doesn't go away and activate it just stays open and i can browse or type to filter but enter does nothing, but occasionaly it does. I can't manage to reproduce it meaningfully
khoata107 commentedon May 10, 2026
/compact are gone too
wangguodong-f commentedon May 10, 2026
I'm really fed up with OpenCode's bugs. The stability of the released software is terrible, there's no quality control at all, and for several consecutive versions, they've reintroduced previously fixed issues into the newly released official versions.
kommander commentedon May 11, 2026
/exit etc. should be back in v1.14.47. I cannot reproduce an issue with /compact.
vparseval commentedon May 12, 2026
Oh. Is /compact context-sensitive by any chance? I don't seem to have it as available command when it would be the first thing in a new session. It's available on the second prompt. If that's intentional, I can understand the rationale but I'd still find it a bit weird.
kommander commentedon May 15, 2026
It is context sensitive, yes. The default behaviour will stay like that. You can make it always visible via a plugin registering a command that just delegates to the compaction command and is always visible.
github-actions commentedon Jul 15, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.