feat(snacks): add snacks.picker action integration

[naowalrahman]

Description

Adds a function under lua/opencode/integrations/picker/snacks.lua that can be used to set up a snacks.picker action that sends the selected/current items to opencode via a keybind.

Note

Line number, if available, is appended to the end of the reference because diagnostic text content usually doesn't have the line number. This is redundant for grep/file references, because the text content for those items do have the line number already, but for the sake of simplicity it is better to just have the line number at the end anyway.

Integration looks like this:

return {
    "folke/snacks.nvim",
    opts = {
        picker = {
            actions = {
                opencode_send = require("opencode.integrations.picker.snacks").opencode_send,
            },
            win = {
                input = {
                    keys = {
                        ["<a-a>"] = {
                            "opencode_send",
                            mode = { "n", "i" },
                        },
                    },
                },
            },
        },
    },
}

Related Issue(s)

• Addresses feat(fzf): add fzf-lua integration for buffer and file selection #138

[Copilot]

Pull request overview

Adds a snacks.picker action integration that sends the currently selected (or fallback) picker items into the opencode prompt.

Changes:

• Introduces opencode_send(picker) action for snacks.picker.
• Builds a newline-delimited list of selected picker entries and appends it to the opencode prompt.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

entry is only populated from item.text. For items where item.file/item.pos exist but item.text is empty (common for many picker items), the code will end up sending just a line ref (e.g. " L10") or dropping the item entirely, which is not a valid opencode file reference. Consider using opencode.context.Context.format({ path = item.file, start_line = ..., start_col = ... }) (and optionally appending item.text as a label) so the output always includes the required @path prefix when a file is available.

Suggested change

	local entries = {}
	for _, item in ipairs(picker:selected({ fallback = true })) do
	local entry = ""
	if item.text and item.text ~= "" then -- Includes file reference
	entry = item.text
	end
	-- Append line numbers if available
	if item.file and item.pos then
	local line_ref = ("L%d"):format(item.pos[1])
	if item.end_pos and item.end_pos[1] ~= item.pos[1] then
	line_ref = line_ref .. ("-L%d"):format(item.end_pos[1])
	end
	entry = entry .. " " .. line_ref
	end
	if entry ~= "" then
	local Context = require("opencode.context").Context
	local entries = {}
	for _, item in ipairs(picker:selected({ fallback = true })) do
	local entry
	-- Prefer constructing a proper opencode context when file and position are available
	if item.file and item.pos then
	local start_line = item.pos[1]
	local start_col = item.pos[2]
	local ctx = Context.format({
	path = item.file,
	start_line = start_line,
	start_col = start_col,
	})
	if item.text and item.text ~= "" then
	entry = ctx .. " " .. item.text
	else
	entry = ctx
	end
	-- Fallback: no file info, just use the text if present
	elseif item.text and item.text ~= "" then
	entry = item.text
	end
	if entry and entry ~= "" then

[Copilot]

This reimplements location formatting manually and only includes line numbers. The project already has Context.format (lua/opencode/context.lua) which handles required spacing for @path references and supports line/column ranges. Reusing it here will avoid subtle formatting bugs and keep location formatting consistent across integrations.

[Copilot]

If no items produce a non-empty entry, this will still call prompt("\n"), which appends an empty line to the TUI prompt. Consider returning early when #entries == 0 (or only adding the trailing newline when there is at least one entry).

Suggested change

	end
	end
	if #entries == 0 then
	return
	end

[dmtrKovalenko]

Updated even though it is limiting the experience. But I think not to much if you don't know about it