[BUG] Header layout updates cause terminals to auto scroll up

[Helmi]

Preflight Checklist

• I have searched existing issues and this hasn't been reported yet
• This is a single bug report (please file separate reports for different bugs)
• I am using the latest version of Claude Code

What's Wrong?

The recently added header that seems to change while using claude code. Switching between the more compact layout and the more detailed one causes some terminals to automatically scroll up (namely xterm.js).

Not sure if this is really considerably a bug but I'd prefer to have the option to disable that at least. It might just be caused by the TUI not realizing its own position in the buffer as this also still happens if the header is far back in the buffer. I don't think it does still update itself on all terminals but it keeps happening on xterm.js and it seems like xterm.js does not offer a way tu suppress this auto scroll behaviour.

Maybe someone can look into this. I'd be glad to help testing

What Should Happen?

Ideally the header should not change when out of visible terminal screen or disabling the changing header would just suppress it.

Error Messages/Logs

Steps to Reproduce

• run claude code in an xterm.js (browser based) terminal.
• launch claude code (2.1.6 confirmed with this behaviour)
• start a conversation
• watch the terminal jumping more or less randomly between header and prompt position.

Claude Model

None

Is this a regression?

I don't know

Last Working Version

No response

Claude Code Version

2.1.6

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Xterm

Additional Information

No response

[Helmi]

To be more precise about the issue, it's switching between these two "headers" (might be the wrong term butr hence the clarification) that i am talking about:

[radaco99]

Having same issue on windows - #20511

[github-actions]

Closing for now — inactive for too long. Please open a new issue if this is still relevant.

[github-actions]

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.