Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[FEATURE] Allow opening terminal without automatically entering insert mode

Open
  • Is something wrong?
#145 4 comments 18 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua, neovim
Domain
tooling

Research direction

Start by tracing how the terminal provider handles focus and insert-mode behavior, then compare the requested terminal.snacks_win_opts values with the existing snacks integration. Done means opening or focusing the terminal can remain in normal mode while the configured terminal options are respected.

Written by the indexing model from the issue text.

Description

Feature Description

I would like an option where when I move my cursor to the terminal, it doesn't automatically enters terminal mode but stays in normal mode

Use Case

I move around a lot and it always trips me up when my navigation buttons do not work anymor because they are trapped by the terminal in neovim.

Proposed Solution

I tried passing these options, I have also set for the snacks terminal, where they work as expected.
It would nice if it would respect those options by default if they are configured in snacks terminal or pass them like this.

---@type LazySpec
return {
	"coder/claudecode.nvim",
	dependencies = { "folke/snacks.nvim" },
	opts = {
		terminal = {
			provider = "snacks",
			snacks_win_opts = {
				start_insert = true,
				auto_insert = false,
				auto_close = true,
			},
		},
	},
	keys = {
		{ "<leader>ac", "<cmd>ClaudeCode<cr>", desc = "Toggle Claude Code" },
		{ "<leader>as", "<cmd>ClaudeCodeSend<cr>", mode = "v", desc = "Send to Claude Code" },
		{ "<leader>ast", "<cmd>ClaudeCodeStatus<cr>", desc = "Claude Code Status" },
	},
}
Dominant language
Lua
Stars
3.1k
Forks
219
No merged PRs in 30d

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

  • No Dockerfile or Docker Compose file
  • No pull request template
  • No contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from coder/claudecode.nvim

All issues in coder/claudecode.nvim

Similar issues

More Lua issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.