[BUG] Claude Code spawns a lot of splited windows

[vtvz]

Bug Description

From time to time (a lot) plugin creates two vertical splits showing diff, but after accepting the one split stays. It can spawn multiple of them and I need to close them one by one using :q. It's very annoying

To Reproduce

Steps to reproduce the behavior:

1. Start using plugin in documented way with provided config without any changes

Expected Behavior

Plugin should use opened window or at least close opened

Environment

• Neovim version: v0.11.4
• Claude Code CLI version: 2.0.36
• OS: ManjaroLinux 25.0.10
• Plugin version: this

Error Messages

No error messages

Additional Context

You can see this behavior in this record starting at 03:24

https://asciinema.org/a/isY9fPKL4lTHZGMsCrvXe8iOP

[ehaynes99]

AFAICT there are 2 cases where this is common:

• if you focus on claude and choose option 3 "no, and tell claude what to do"
• if it wants to edit a file that you do not currently have in an open buffer, it appears to open the file in a new split pane, then split again to show the diff such that when you accept, it goes back to the additional split

[andyl]

I'm happy with claude's diff presentation and don't want claudecode.nvim to create the diff view in neovom. How can this be done?

[simozampa]

use open_in_currrent_tab = flase to avoid claude from opening new windows

opts = {
      diff_opts = {
        auto_close_on_accept = true, -- Close diff windows after accepting
        vertical_split = true, -- Use vertical splits for diffs
        open_in_current_tab = false, -- Don't create new tabs
        keep_terminal_focus = true, -- Keep focus on Claude terminal
      },
    },

[SachaMPS]

open_in_currrent_tab = false, unfortunately doesnt prevent this in my case somehow :(

[mieubrisse]

I'm experiencing this same problem:

1. Claude opens a Vimdiff (amazing, I'm happy with this in my case)
2. I :w to accept
3. Claude continues, but one of the splits stays around and I have to manually close it

It'd be great if, when accepting or rejecting, the plugin closes both splits.

[ehaynes99]

open_in_currrent_tab = false, unfortunately doesnt prevent this in my case somehow :(

You have a typo open_in_currrent_tab (three rs).

A couple of clarifications. First off, open_in_current_tab is called "legacy" in the code, but the replacement open_in_new_tab (which makes more sense, since the other for false means "don't not open it in the current tab") is not mentioned in the readme.

claudecode.nvim/lua/claudecode/config.lua

Lines 212 to 215 in 93f8e48

	-- Map open_in_current_tab -> open_in_new_tab (legacy option takes precedence)
	if type(d.open_in_current_tab) == "boolean" then
	d.open_in_new_tab = not d.open_in_current_tab
	end

But more importantly, "tab" in vim doesn't mean what most people think of today. It's basically a whole new "virtual window layout" that's isolated from the others. Nowadays, a lot of people use something like bufferline to simulate what most of us think of as "tabs", but is actually showing buffers with familiar tab-like labels.

This setting doesn't technically fix the issue, but I think the behavior is actually better anyway. open_in_new_tab means the plugin creates its own tab ("virtual window layout"), displays 3 panes of the diff plus claude. When you accept/reject, it throws that tab away and goes back to your main tab where you have whatever splits/windows you had before, fully intact.

Honestly I'm not even sure it's worth trying to fix this bug vs. just getting rid of the option. It's really difficult for plugins to try to muck with your existing window layout, and even harder to set it back, especially since you could have changed it in the interim. e.g. where should it render the diff here?

[ThomasK33]

Hey, could you let me know if #175 (branch nvim-integration-xg1c) fixes this for you?

[SachaMPS]

@ThomasK33 i am using the mentioned branch since yesterday and will post here again in a couple of days?! Thank you

[SachaMPS]

@ThomasK33 For me this works. But it might be not everyones use case: I use claude from another terminal window and not in nvim directly anymore to circumvent formatting errors in claudes output caused by something else.

[tomerlevy1]

Hey
I can confirm that this fix is also working for me