[Bug] Text input lag and garbled output when switching between Claude Code and Neovim
Status Fixed / completed
Maintainer reply None cached
Activity 10 comments · opened Nov 4, 2025 · closed Dec 2, 2025
Bug Description
After updating to the latest v2.0.32, in general text input in nvim is slow. Likely this is because inputs are processed in claude-code when I'm switching from it. This occurs as well when I press shortcut keys.
Related issue #10735 #10375
Then, after I return to claude-code by exiting nvim, sometimes there are some garbled text that's likely coming from nvim.
How to reproduce
- Setup nvim + LazyVim (just use the most basic settings: https://www.lazyvim.org/installation)
- Use
ctrl+gshortcut to edit prompt using claude-code
I'm using nvim + LazyVim
Environment Info
- Platform: darwin
- Terminal: ghostty
- Version: 2.0.32
- Feedback ID: 8f44f24a-0cc6-4351-bcdb-5b02a22a54bd
10 Comments
Found 3 possible duplicate issues:
This issue will be automatically closed as a duplicate in 3 days.
🤖 Generated with Claude Code
Here's some of the sample outputs when I exit
:qnvim instead of save and quit:wqIt does seem the issue isn't specific to v2.0.32, I can still observe the lag compared to if I just open nvim directly, without using
ctrl+g. I have disabled blink.cmp on markdown files if it's related, but the lag is still there.the lag was gone when i switched to non-native installation
That's an interesting finding. I found the local installation tend to be more stable than the native
Same experience here. When starting neovim via ctrl-g from the native installation, it's not just laggy but completely misses a lot of keystrokes. When installing via pnpm I don't have this problem.
Using wezterm on MacOS 26.0.1
Bun 1.3 fixed some issues that look similar to this (https://github.com/oven-sh/bun/issues/10694), where Bun would not correctly release a
readlineinstance and so it would continue to grab characters from stdin even when other things (i.e. the nvim subprocess) are also reading input.Not sure which Bun version Claude Code native is using, or if this is actually the problem, but potentially this could be fixed by updating the native build to use 1.3.
@dimfeld Do you still observe the same issue in 2.0.53? Looks like it's fixed
I had the same issue. Tested again on v2.0.55, and it seems to be fixed.
Just reinstalled the native build to try it out, and it's fixed on my end too :)
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.