feature: reference rules in `ask`

[garma-a]

Did you check docs and existing issues?

• I have read the plugin docs
• I have read the opencode docs
• I have searched the existing plugin issues
• I have searched the existing opencode issues

:checkhealth opencode output

============================================================================== opencode: require("opencode.health").check() opencode.nvim ~ - OS: Linux 6.14.0-37-generic (x86_64) - nvim version: 0.11.0+ga99c469e54. - opencode.nvim git commit hash: ed2a936b163df9e92ef210daad3a9ae89ca7e073. - vim.g.opencode_opts: { events = { reload = true }, port = 12000, provider = { cmd = "env OPENCODE_DISABLE_FILETIME_CHECK=true opencode --port", enabled = false, snacks = { win = { width = 0 } }, terminal = { width = 0 } } } opencode.nvim [binaries] ~ - OK opencode available with version 1.1.48. - OK curl available. opencode.nvim [snacks] ~ - OK snacks.input is enabled: ask() will be enhanced. - OK snacks.picker is enabled: select() will be enhanced. opencode.nvim [providers] ~ - WARNING No opencode provider configured. - OK The snacks provider is available. - WARNING The kitty provider is not available — KITTY_LISTEN_ON environment variable is not set. - ADVICE: - Enable remote control in kitty. - WARNING The wezterm provider is not available — wezterm executable not found in $PATH. - ADVICE: - Install wezterm and ensure it's in your $PATH. - WARNING The tmux provider is not available — Not running in a tmux session. - ADVICE: - Launch Neovim in a tmux session. - OK The terminal provider is available.

Describe the bug

in normal terminal session i can use the / command to reference my context files often located in
~/.config/opencode/commands but for some reason inside the inline prompt using this plugin i cannot use the **/ ** letter to reference any thing

Steps To Reproduce

1. open neovim
2. try to excute or open inline ask
3. try to type / followed by the file name for your context files

Expected Behavior

it should work as normal TUI opencode's session so i can reference my context files and inject them to the current prompt

[nickjvandyke]

"Context files" isn't clear to me - are you referring to https://opencode.ai/docs/commands or https://opencode.ai/docs/rules/ ?

[garma-a]

"Context files" isn't clear to me - are you referring to https://opencode.ai/docs/commands or https://opencode.ai/docs/rules/ ?

i was actually referring to https://opencode.ai/docs/commands using forward slashes here 👇

require("opencode").ask("@this: ", { submit = true })

[nickjvandyke]

Thanks for clarifying!

So you're proposing we fetch the command's body and inject that when the opencode.nvim prompt contains /<custom-command?

I think this is already covered by the plugin's configured prompts. You should copy any commands to those (vim.g.opencode_opts = { prompts = ... }, and add context placeholders as needed.

It would be nice to share a single source of prompts between the plugin and opencode, but would take a lot of duplicate work and possibly still not be a better UX in the end. Not to mention that it'd be impossible to support the agent and model field from OC's configured commands. I'm open to ideas that I may be missing though!

FWIW the select menu will fetch and include custom commands. Although I don't think opencode's server actually accepts them right now. And I realize that wouldn't allow for editor context injection.

Idk everyone's workflow, but I think the prompts you want to use from your editor are often different from the ones you'd use in the TUI anyway. So in a way, the lack of mixing is a plus.

[nickjvandyke]

(If anything, I think it should be on opencode to interpret TUI-appended slash commands. That's much more scalable and maintainable than us implementing it)