#106 [Bug] Threads list and messages view glitches

[Anonymous]

Originally created by: supreme-gg-gg
Originally owned by: endernoke

Describe the bug
Typescript client chat view randomly glitches whenever you:

1. Navigate between threads (j/k)
2. Type anything in the Input Box in the messages view

I suspect this is just over re-rendering as some random prop changes and resulting in this "glitch", but I cannot find what is causing this, any evidence of this being the cause, or any potential solution...

To Reproduce
Steps to reproduce the behavior:

1. npm run build
2. npm run start chat
3. navigate threads -> Enter
4. Type something in input bar

Expected behavior
This should be fixed and work like the python client! this is a big UI UX bug!

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: [e.g. iOS]
• Browser [e.g. chrome, safari]
• Version [e.g. 22]

Smartphone (please complete the following information):

• Device: [e.g. iPhone6]
• OS: [e.g. iOS8.1]
• Browser [e.g. stock browser, safari]
• Version [e.g. 22]

Additional context
Add any other context about the problem here.

[Anonymous]

Originally posted by: supreme-gg-gg

See https://github.com/vadimdemedes/ink/issues/263

[Anonymous]

Originally posted by: endernoke

also see:
https://github.com/vadimdemedes/ink/issues/359

https://github.com/anthropics/claude-code/issues/1913

https://github.com/oclif/multi-stage-output/pull/11

[Anonymous]

• assigned_to: supreme-gg-gg

[Anonymous]

• assigned_to: endernoke

[Anonymous]

Originally posted by: endernoke

This is probably not caused by:

• UI re-rendering
• using alt screens for TUI (I tested both with and without entering alt screen and the issue and fix are the same)

We suspect this is an issue with Ink's handling of stdin.

A workaround is to set screen height to exactly one line less than process.stdout.rows, (see https://github.com/vadimdemedes/ink/issues/450) which leaves the bottom-most line untouched for Ink to read/clear stdin. This would fix most of the flickering.

A complete solution would most likely require changing Ink's internal input handling. This will be investigated.

[Anonymous]

Originally posted by: endernoke

This is probably not directly related to UI re-rendering. We suspect this is an issue with Ink's handling of stdin.

A workaround is to set screen height to exactly one line less than process.stdout.rows, (see [vadimdemedes/ink#450](https://github.com/vadimdemedes/ink/issues/450)) which leaves the bottom-most line untouched for Ink to read/clear stdin. This would fix most of the flickering.

A complete solution would most likely require changing Ink's internal input handling. This will be investigated.

I see Gemini CLI dev team is working on this issue so let's see hopefully it will be fixed soon.

[Anonymous]

Originally posted by: supreme-gg-gg

Close as completed in [#111]

[Anonymous]

Ticket changed by: supreme-gg-gg

• status: open --> closed