You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Ending prompt with an absolute path blocks starting inference. #54190
Thanks for the clear report! I can reproduce this on 2.0.20, and it still happens on the latest v2 branch (d2905b8).
Steps: type list files in /tmp in the prompt with no trailing space. The slash-command popup opens with No matching commands, and Enter does nothing. The prompt isn't sent. The recording and screenshot below show this, and the script below reproduces it.
From the code, a / typed after a space starts a slash-command lookup, as long as no space or second / follows it. While that popup is open, Enter is ignored even when no command matches. Until this is fixed, these should work around it: quote the path (as you found), add a trailing space or other text after the path, or press Esc to close the popup before pressing Enter.
recording.mp4
Reproduction script (drive.ts)
// Reproduces anomalyco/opencode#54190: a prompt ending with an absolute path// (e.g. "list files in /tmp") opens the slash-command menu ("No matching commands")// and Enter does not submit the prompt.import{Effect}from"effect"import{OpenCodeDriver}from"opencode-drive"exportdefaultOpenCodeDriver.use({
...(process.env.OC_DEV ? {opencode: {dev: process.env.OC_DEV}} : {}),tui: {recording: true,keypressOverlay: true},},({ ui })=>Effect.gen(function*(){yield*ui.screenshot("01-home")yield*ui.type("list files in /tmp")yield*Effect.sleep(800)yield*ui.screenshot("02-typed")yield*ui.enter()yield*Effect.sleep(2000)yield*ui.screenshot("03-after-enter")constframe=yield*ui.capture()consttext=JSON.stringify(frame)constmenu=text.includes("No matching commands")// No LLM response is queued: if the prompt were submitted, Drive would report an unexpected request.constanswered=text.includes("Thinking")||!text.includes("list files in /tmp")yield*Effect.log(`menu visible after Enter: ${menu}; response shown: ${answered}`)if(!menu||answered)returnyield*Effect.fail(newError("Did not reproduce: prompt was submitted"))yield*Effect.log("REPRODUCED: Enter did not submit; 'No matching commands' shown")}),)
Run it with opencode-drive: opencode-drive run ./drive.ts. It drives opencode from your PATH; set OC_DEV to the path of an OpenCode checkout to run that from source instead.
Fixed by #54857, released in v2.0.28: the command menu now only opens when / is at the start of the prompt, so a prompt that ends in a path like /tmp sends normally. If you still see this on v2.0.28 or later, comment and we'll reopen.
Activity
opencode-agent commentedon Oct 9, 2026
Thanks for the clear report! I can reproduce this on 2.0.20, and it still happens on the latest
v2branch (d2905b8).Steps: type
list files in /tmpin the prompt with no trailing space. The slash-command popup opens with No matching commands, and Enter does nothing. The prompt isn't sent. The recording and screenshot below show this, and the script below reproduces it.From the code, a
/typed after a space starts a slash-command lookup, as long as no space or second/follows it. While that popup is open, Enter is ignored even when no command matches. Until this is fixed, these should work around it: quote the path (as you found), add a trailing space or other text after the path, or press Esc to close the popup before pressing Enter.recording.mp4
Reproduction script (drive.ts)
Run it with opencode-drive:
opencode-drive run ./drive.ts. It drivesopencodefrom yourPATH; setOC_DEVto the path of an OpenCode checkout to run that from source instead.neriousy commentedon Oct 20, 2026
Fixed by #54857, released in v2.0.28: the command menu now only opens when
/is at the start of the prompt, so a prompt that ends in a path like/tmpsends normally. If you still see this on v2.0.28 or later, comment and we'll reopen.