Repository navigation
[Experimental] : Implementing new features by some kind of recipes approach #536
Description
I've found that I already prefer typing in opencode.nvim (due to some blink and add_context features), but there's a plugin in the TUI that's quite interesting.
https://libraries.io/npm/opencode-quick-quote
You can quickly reference a specific message by using ">" for a fuzzy search
Although it might also be a "pseudo-need," after all, it isn't slow for me to select the context I'm interested in and manually copy and paste it, or add_visual_selection
Huh, it turns out add_visual_selection doesn't support opencode.output-window (well, I just remembered now)
As an experiment, this kind of functionality should be easy to implement with recipes. Existing features could perhaps also be organized as “built-in recipes.”
Activity
jensenojs commentedon Oct 16, 2026
Treating features as recipes reduces maintenance costs in every way and lets us make as few changes to the core code as possible.
sudo-tee commentedon Oct 16, 2026
I like the idea. In order for opencode.nvim to support this we need to add more extension points.
eg.
custom formatterscustom completioncustom contextetc. so people are inclined into building their workflow instead of maintaining every workflow possible.We need to come up with a plan for extensibility and which api are needed to achieve that. After that we can write up some nive reciepes for the plugin.