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

[FEATURE] Allow A ClaudeCode-Per-Tab

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

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
lua, neovim
Domain
developer-experience, tooling

Research direction

Start at the :ClaudeCode command and compare its behavior across the :tabnew examples in this issue, then review the related issue 187. Done means separate Neovim tabs can each create and manage an independent Claude Code window, either through repeated :ClaudeCode calls or a command such as :ClaudeCodeFromThisWindow.

Written by the indexing model from the issue text.

Description

Feature Description

:ClaudeCode appears to only work in the current tab. This is somewhere between a bug and a feature request but basically people should be able to make at least one Window of ClaudeCode per-tab.

:tabnew
:ClaudeCode
:tabnew
:ClaudeCode

(Creates 2 separate windows)

Currently if you try to Neovim tabs give a different view for buffers (e.g. :tabnew). Currently if you call :ClaudeCode, it
A clear and concise description of what you'd like to see added to the plugin.

Use Case

Though I'd love to just use tmux, it's not always available. When that happens, I use Neovim tabs.

And just in general being able to have more than one Claude Code open in a single Neovim instance would be generally useful

Proposed Solution

If a new command like :ClaudeCodeFromThisWindow or something was created, I could manage the windows myself programmatically.

Alternatives Considered

Possibly related: https://github.com/coder/claudecode.nvim/issues/187

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.