Summary
There is no dedicated one-off command for arbitrary read-only questions to OpenCode. Users can route through /opencode:rescue, but that command is framed as task delegation and defaults to write-capable behavior unless read-only is requested.
This is distinct from #25 (/opencode:consult), which tracks persistent multi-turn Q&A sessions. /opencode:ask would be ephemeral and single-shot.
Proposed UX
/opencode:ask explain the auth flow in this repository
/opencode:ask what would break if we switched this API from REST to gRPC?
Expected behavior:
- forwards the user's prompt to OpenCode with repo context
- uses a read-only agent/tool configuration
- returns OpenCode's answer verbatim or lightly rendered
- does not persist a consult session
- does not write files
Why this helps
It gives users a low-friction path for questions that are not reviews and not implementation tasks.
Upstream reference
Derived from openai/codex-plugin-cc#9.
Summary
There is no dedicated one-off command for arbitrary read-only questions to OpenCode. Users can route through
/opencode:rescue, but that command is framed as task delegation and defaults to write-capable behavior unless read-only is requested.This is distinct from #25 (
/opencode:consult), which tracks persistent multi-turn Q&A sessions./opencode:askwould be ephemeral and single-shot.Proposed UX
Expected behavior:
Why this helps
It gives users a low-friction path for questions that are not reviews and not implementation tasks.
Upstream reference
Derived from openai/codex-plugin-cc#9.