[BUG] Integration with Lazyvim's Snack terminal does not allow the window to be resized or change width configuration

[ottawafunsports]

Bug Description

I'm using Lazyvim configs in my nvim (just default configs) and I've noticed that I cannot change the ClaudeCode terminal window through our current configs. If I change it in either snacks or claudecode config, it doesn't seem to work either way.

It does work if I just use native as my ClaudeCode terminal but the integration is not as nice as using Snacks.

To Reproduce

Steps to reproduce the behavior:

1. Set up ClaudeCode lua config file in lazyvim configs
2. Set split_width_percentage in terminal opts
3. Start Claude Code integration and notice the window size is unchanged

-- Note it's interesting that split_side does work

Expected Behavior

The window width should change according to configs. And you should be able to resize it within nvim.

Environment

• Neovim version: 0.11.2
• Claude Code CLI version: 1.0.51
• OS: macOS 15.6
• Plugin version: 0.2.0

[vinidlidoo]

+1

[JordanFaust]

I ran into the same issue. The problem turned out to be the configuration of edgy within LazyVim.

Specifically I was attempting to make changes with the width of the terminal on the right. The above linked configuration was configuring edgy for the snacks terminal in such a way that it took precedence over what I was attempting to configure via this plugin

[Shiu]

I believe the problem is nvim-tree's resize function interfering with the claude terminal width.. nvim-tree calls vim.api.nvim_win_set_width() and sometimes :wincmd during file operations which then overrides the the terminal width and you get either a very wide terminal around 230characters, or a 1 character terminal.

The root cause seems to be in nvim-tree/view.lua:385 where any resize operation affects all windows.

You can test this by temporarily disabling nvim-tree in your config and see if the terminal width issue disappears.

I didn't do much testing yet, but I've got a hacky workaround that's been working for me even when doing very rapid resizing. It's not a permanent solution though.

[johnMocingbird]

Same issue here.