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

[BUG] Hardcoded terminal buffer filter breaks with external terminal setups

Open
  • Is something wrong?
#206 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
50/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Stale
Tech stack
lua, neovim
Domain
tooling

Research direction

Start in selection.lua and reproduce the setup with terminal.provider = "none" and sidekick.nvim using the tmux backend. Check how the terminal buffer is identified and verify that selecting it retains the last active code buffer instead. Confirm the fix with the described reproduction steps.

Written by the indexing model from the issue text.

Description

Bug Description

The terminal buffer filter in selection.lua is hardcoded to only match buffers containing "claude" in their name. When Claude Code runs via sidekick.nvim with mux.backend = "tmux", the terminal buffer is named term://...tmux - it never contains "claude". As a result, selection tracking treats the tmux terminal as an active code buffer instead of ignoring it.

I have a fix ready and will open a PR shortly.

To Reproduce

  1. Configure claudecode.nvim with terminal.provider = "none"
  2. Launch Claude Code via sidekick.nvim with tmux backend
  3. Switch cursor to the Claude Code terminal pane
  4. Selection tracking reports the tmux terminal buffer instead of the last active code file

Expected Behavior

Selection tracking should ignore the terminal buffer and retain the last active code buffer, regardless of how Claude Code was launched.

Environment

n/a - the issue is in the Lua filter logic, independent of versions.

Error Messages

No error messages. The filter silently fails to match.

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.