Slash commands are not resolved when using "opencode run"

[jgordijn-ah]

Description

When running OpenCode interactively, slash commands (e.g. /mycmd) are correctly resolved by OpenCode before being sent to the LLM. The command is expanded or executed internally, and only the resolved result is passed to the model.

However, when using opencode run, slash commands are not resolved. Instead, the raw slash command (e.g. /mycmd) is forwarded verbatim to the LLM. Since the LLM has no knowledge of OpenCode-specific slash commands, it responds with a hallucinated error message.

This results in inconsistent behavior between interactive and non-interactive usage and makes opencode run unreliable for automation.

Expected Behavior

opencode run should behave the same as interactive mode.

Why this matters (Ralph Wiggum workflow)

This behavior is particularly annoying when using Ralph Wiggum–style workflows, where OpenCode is run repeatedly in a loop. I would like to run a slash command in a loop, without workaround

Plugins

No response

OpenCode version

1.1.6

Steps to reproduce

1. Define a custom command /mycmd with the content: Say hello to the user
2. Run OpenCode interactively and invoke /mycmd - Observe that the command is resolved and executed correctly
3. Run:

opencode run "/mycmd"

Result:

Screenshot and/or share link

No response

Operating System

MacOS

Terminal

Ghostty

[github-actions[bot]]

This issue might be a duplicate of existing issues. Please check:

• #7000: Slash commands are being incorrectly captured
• #7337: Custom TUI actions/keybinds for shell commands (related automation feature request)

Feel free to ignore if none of these address your specific case.

[rekram1-node]

@jgordijn-ah use the "--command mycmd" and it works we dont resolve the /mycmd we expect the flag, we may change that tho

[jgordijn-ah]

Ok, thanks. I missed that one. You may close this issue or keep it if you want to change that behavior. I'll leave that up to you.