[FEATURE] send and focus in one command

[mwojick]

Feature Description

I want to trigger both ClaudeCodeSend (or ClaudeCodeAdd) and ClaudeCodeFocus in one command. Tried doing something like "<cmd>ClaudeCodeSend<cr><cmd>ClaudeCodeFocus<cr>" but it doesn't work.

Use Case

A lot of the time I just want to send one snippet and go straight to the terminal.

[alex35mil]

I implemented a workaround in my config.

[junheep-dev]

Yeah, it would be a useful feature.
Here's my workaround:

      {
        "<leader>as",
        function()
          vim.cmd("ClaudeCodeSend")
          vim.defer_fn(function()
            vim.cmd("ClaudeCodeFocus")
          end, 0)
        end,
        mode = "v",
        desc = "Send (ClaudeCode)",
      },

[mwojick]

Thanks, actually what I realized is that the send command is inconsistent since it does auto focus the terminal when it's hidden, but doesn't when it's open. So I would propose by default not focusing the term, and focusing with a flag like ClaudeCodeSend --focus

Anyway I landed on a workaround that is a combination of the two above + using the fact that send will already send+focus when not visible, since just doing the defer workaround only works when the term is visible. You will probably have to adjust is_claude_buf depending on your term provider. Also if you want the opposite functionality (i.e. just send, don't focus), you can just invert the conditional and it somehow works:

---@return boolean
local function is_claude_buf(bufid)
	if not vim.api.nvim_buf_is_loaded(bufid) then
		return false
	end

	local buf_info = vim.fn.getbufinfo(bufid)[1]

	local term_title = buf_info.variables.term_title
	if term_title and type(term_title) == "string" then
		return string.find(term_title, "claude") ~= nil
	end

	return false
end

---@return boolean
local function is_claude_visible()
	local current_tab = vim.api.nvim_get_current_tabpage()
	local windows = vim.api.nvim_tabpage_list_wins(current_tab)

	for _, win in ipairs(windows) do
		local buf = vim.api.nvim_win_get_buf(win)
		if is_claude_buf(buf) then
			return true
		end
	end

	return false
end

return {
	"coder/claudecode.nvim",
	dependencies = { "akinsho/toggleterm.nvim" },
	config = function()
		require("claudecode").setup({
			terminal = {
				provider = setup_toggleterm_provider(),
			},
		})
	end,
	keys = {
		{
			"<leader>as",
			function()
				if is_claude_visible() then
					vim.cmd("ClaudeCodeSend")
					vim.defer_fn(function()
						vim.cmd("ClaudeCodeFocus")
					end, 50)
				else
					vim.cmd("ClaudeCodeSend")
				end
			end,
			mode = "x",
			desc = "Send and Focus ClaudeCode",
		},
	},
}

[mwojick]

actually after trying it more I realized even when the term is open, the defer is inconsistent and sometimes it doesn't focus, so maybe a more complicated solution like what alex has is needed

[ThomasK33]

Hey @mwojick, thanks for opening this issue.

If I remember correctly, this used to be the default behavior in 0.1.0, but I cannot remember why I changed it 😅
Anyway, let me know if #118 does what you're looking for.

[mwojick]

Hey @ThomasK33 , thanks for the reply. Is it possible for this setting to be on the command level rather than global?

[ThomasK33]

Hey @ThomasK33 , thanks for the reply. Is it possible for this setting to be on the command level rather than global?

What do you mean by command level?

[mwojick]

So sometimes I want to just send, like if I'm adding multiple things to context, but with a different keybind I want to situationally send+focus together. If it's global I can only do one or the other (I think)

[ThomasK33]

So sometimes I want to just send, like if I'm adding multiple things to context, but with a different keybind I want to situationally send+focus together. If it's global I can only do one or the other (I think)

Gotcha. In that case, you should write a Lua keymapping yourself.

-- Example 1: Send file and focus terminal
vim.keymap.set('n', '<leader>cf', function()
  local claudecode = require('claudecode')
  local terminal = require('claudecode.terminal')

  -- Send the file

claudecode.send_at_mention(vim.fn.expand('%:p'))

  -- Manually focus the terminal
  terminal.open()
end)

-- Example 2: Send file without focusing (just 
ensure visible)
vim.keymap.set('n', '<leader>cs', function()
  local claudecode = require('claudecode')
  local terminal = require('claudecode.terminal')

  -- Send the file

claudecode.send_at_mention(vim.fn.expand('%:p'))

  -- Just ensure terminal is visible, don't focus
  terminal.ensure_visible()
end)

-- Example 3: Send with selection and focus
vim.keymap.set('v', '<leader>cf', function()
  local claudecode = require('claudecode')
  local terminal = require('claudecode.terminal')

  local start_line = vim.fn.line("'<")
  local end_line = vim.fn.line("'>")


claudecode.send_at_mention(vim.fn.expand('%:p'),
start_line, end_line)
  terminal.open()
end)

[mwojick]

Thanks, that gave me a good starting point but I needed to do a bit extra to get it to work properly:

local function send_and_focus()
	local claudecode = require("claudecode")
	local terminal = require("claudecode.terminal")

	local esc = vim.api.nvim_replace_termcodes("<ESC>", true, false, true)
	vim.api.nvim_feedkeys(esc, "nx", false)

	local start_line = vim.fn.line("'<")
	local end_line = vim.fn.line("'>")

	local claude_start_line = start_line and (start_line - 1) or nil
	local claude_end_line = end_line and (end_line - 1) or nil

	claudecode.send_at_mention(vim.fn.expand("%:p"), claude_start_line, claude_end_line)
	terminal.open()
end

Also needed to modify my open and ensure_visible methods of my term provider. No idea why the -1 is needed on the lines but I saw you were doing that in the source code too. Anyway I guess this is a bit more robust than the defer hack I was doing before but could be made easier if there was a builtin command. Also somewhat related but it seems like the queue_mention isn't working anymore (i.e. add/send something before the term is connected -> doesn't add it after connection starts). Maybe to do with new version of Claude Code (I'm on 1.0.77). If you want a separate issue for that let me know.

[mwojick]

ok looks like the last bit I mentioned has been fixed in 1.0.80