Terminal display rendering incorrectly with overlapping or duplicated text elements

[ElleNajt]

I'm using vterm and sometimes this happens:

This seems to mostly happen when the buffer gets resized, often when I switch from my desk monitor to my laptop monitor, but it's intermittent. Has anyone else run into this? Any ideas about how to fix it?

Possibly related to claude-code--vterm-multiline-buffer-filter ? I'm not sure if I get this when I run claude in a terminal without claude-code.el

Thanks!

[stevemolitor]

You can turn off claude-code--vterm-multiline-buffer-filter by setting claude-code-vterm-buffer-multiline-output to nil.

I have seen that on occasion but not often. I think it happens running CC in vanilla vterm as well, but not when running claude in an external terminal IIRC.

[ElleNajt]

Hmm, toggling that off doesn't seem to help, at least for a buffer that's already malfunctioning in this way.

When I start a new claude code buffer when just on my laptop screen things are fine. But the ones that come from a large monitor end up with the text box wrapping (I think) like this:

[stevemolitor]

Well, thanks for checking. It's good to know that claude-code--vterm-multiline-buffer-filter doesn't seem to be the culprit.

Can you make it go away by resizing the buffer, making it wider and narrower? Or does it stay messed up? Does toggling read-only mode help?

Or is the only remedy to kill and restart with claude-code-continue?

[Andsbf]

The same is happening to me, I'm using eat, I hope it helps in the troubleshooting process.

[ElleNajt]

Or is the only remedy to kill and restart with claude-code-continue?

One work around here could be a command to seamlessly kill the claude session and resume the same session. Seems feasible if we can get the session ID out of the vterm/eat buffer.

Can you make it go away by resizing the buffer, making it wider and narrower? Or does it stay messed up?

Making the buffer larger can make the issue go away, yeah.

Does toggling read-only mode help?

(Will check next time I encounter it, the usual things are not triggering it now ... which is good?)

[brandon-arnold]

Here's the workaround I'm using, for now:

1. Once a claude session is started at a certain window width, you need to keep that window width for the rest of the session (or fix it back if the width ever changes).
2. Pay attention to anything that may affect window width, especially showing line numbers. (global-display-line-numbers-mode) was turned on for me, so as soon as the line numbers went from 2 to 3 digits, it starts messing up. So I added (add-hook 'claude-code-start-hook (lambda () (display-line-numbers-mode -1))) to the :config section of my claude-code use-package.