Skip to content

Got two input buffers when I resize the nvim window #144

Closed

Description

@vipware

When I resize the neovim window, I got two chatting input buffers .

Image

Activity

  1. sudo-tee commented on Dec 18, 2025

    @sudo-tee
    Owner

    Thanks for the report
    This is rather strange,

    Can you give me your full opencode plugin config ?

    Are you sure the setup is not called twice ?

    Does this happen everytime ?

  2. vipware commented on Dec 18, 2025

    @vipware
    Author

    Thank you for your reply, and also thank you for developing such an excellent Neovim plugin. Below is my whole configuration in Neovim version 0.12:

    vim.pack.add({ { src = "https://github.com/sudo-tee/opencode.nvim" } })
    require("opencode").setup({
    	preferred_picker = "telescope",
    	preferred_completion = "blink",
    	default_global_keymaps = true,
    	default_mode = "build",
    	ui = {
    		icons = {
    			preset = "nerdfonts",
    			overrides = {
    				header_user = "", 
    				header_assistant = " 󰟍 ", 
    				search = "FIND", 
    				border = "|", 
    			},
    		},
    		input = {
    			text = {
    				wrap = true, 
    			},
    		},
    	},
    	context = {
    		enabled = true, 
    		cursor_data = {
    			enabled = false,
    		},
    		diagnostics = {
    			info = false, 
    			warn = true, 
    			error = true, 
    		},
    		current_file = {
    			enabled = true,
    		},
    		selection = {
    			enabled = true,
    		},
    	},
    	hooks = {
    		on_file_edited = nil, 
    		on_session_loaded = nil, 
    		on_done_thinking = nil, 
    		on_permission_requested = nil, 
    	},
    })
    

    Thanks for the report This is rather strange,

    Can you give me your full opencode plugin config ?

    Are you sure the setup is not called twice ?

    Does this happen everytime ?

  3. sudo-tee commented on Dec 19, 2025

    @sudo-tee
    Owner

    Does this happen everytime ?

    I am still not able to reproduce it

  4. vipware commented on Dec 19, 2025

    @vipware
    Author

    I have tried in Item2/wezterm/ghostty, it happens everytime.

  5. sudo-tee commented on Dec 19, 2025

    @sudo-tee
    Owner

    Mind sharing a screen recording of it ? Maybe I could see what is going on

  6. sudo-tee commented on Dec 23, 2025

    @sudo-tee
    Owner

    @vipware

    I am still not able to reproduce it.

    Do you have a video or do you have a link to your full nvim config ?

  7. vipware commented on Dec 24, 2025

    @vipware
    Author

    @vipware

    I am still not able to reproduce it.

    Do you have a video or do you have a link to your full nvim config ?

    https://youtu.be/huhYmaIneW0

  8. sudo-tee commented on Dec 24, 2025

    @sudo-tee
    Owner

    I don't have access

    Image
  9. vipware commented on Dec 30, 2025

    @vipware
    Author

    I don't have access

    Image

    Please, try again.

  10. jinzhongjia commented on Jan 2, 2026

    @jinzhongjia
    Contributor

    That's very strange, I also can not reproduce this issue.

  11. sudo-tee commented on Jan 2, 2026

    @sudo-tee
    Owner

    @vipware Are your setup locked to an older version ?

    Have you try to update the plugin ?

  12. muromeo1 commented on Jan 14, 2026

    @muromeo1

    Hey guys! It happens for me as well. Usually, it happens when I open or close a new pane on tmux. I'm using vim-tmux-navigator, not sure if it can be related.

    Image

  13. sudo-tee commented on Jan 15, 2026

    @sudo-tee
    Owner

    I am still not able to reproduce even witht tmux :/

    Are you using the latest version of the plugin ?

  14. muromeo1 commented on Jan 19, 2026

    @muromeo1

    Are you using the latest version of the plugin ?

    Yeap, I quickly update all my plugin versions whenever a new version comes out.
    If it helps, this is my updated dev setup:

    https://github.com/muromeo1/dotfiles

  15. muromeo1 commented on Jan 19, 2026

    @muromeo1

    But either way, it's a minor. Whenever this happens, I just close and re-open the panel and everything looks normal again.

  16. disrupted commented on Jan 25, 2026

    @disrupted
    Contributor

    in my config this autocmd was the cause. I've disabled it for now

    vim.api.nvim_create_autocmd('VimResized', {
        desc = 'resize splits when Vim is resized',
        callback = function()
            local current_tab = vim.api.nvim_get_current_tabpage()
            vim.cmd 'tabdo wincmd ='
            vim.api.nvim_set_current_tabpage(current_tab)
        end,
    })
  17. sudo-tee commented on Jan 25, 2026

    @sudo-tee
    Owner

    This could give me a hint on what is happening

    Thanks for the comment

  18. disrupted commented on Feb 3, 2026

    @disrupted
    Contributor

    @vipware @muromeo1 could you give #233 a try? this should hopefully fix the issue for you too

  19. added a commit that references this issue on Feb 5, 2026
    574c536
  20. sudo-tee commented on Feb 5, 2026

    @sudo-tee
    Owner

    @disrupted @vipware @muromeo1

    I created another MR with a more robust approach for duplicated window. It should also covers trying to split the opencode windows.

  21. sudo-tee commented on Feb 5, 2026

    @sudo-tee
    Owner

    I closed the issue and merged the fix.

    If there is still issues please let me know and I will reopen

  22. added a commit that references this issue on Feb 5, 2026
    1e57036
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions