CommandCodeAI / CommandCodeAI/desktop

[Bug]: scroll keeps jumping around, making the app very hard to use.

Open
#20 14 comments 0 reactions 1 assignee View on GitHub

@aliarain is already working on this.

Since Aug 13, 2026.

bug
Dominant language
Shell
Stars
80
Forks
2
PR merge metrics
No merged PRs in 30d

Description

GUI version

0.1.8

Operating system

macOS (Apple silicon)

Reproduction steps

Perform any coding task which uses a decent number of tokens where the conversation is a few screens long.
Once scroll comes into play, the screen jumps automatically.
Meaning I'm never at the end of the conversation where I have typed new instructions. The box to type in prompt stays stationary, but the rest of the window (LLM response) jumps up and down. Making it almost impossible for me to read what the LLM had to say to my last prompt.
The jumping happens every time you scroll past a complete response of the LLM.
The down arrow button to take you to the end of the chat also does not bring you to the end of the chat in such scenarios.

Expected behavior

Smooth scrolling.
No jumps in scrolling.
If while scrolling you hit the bottom of the chat, the scroll shouldn't jump back up into middle of the chat.
If while scrolling you scrolled up to a particular response the scroll shouldn't jump around.
The down arrow should bring you to the bottom of the chat, and not cause the chat response to jump around randomly.

Actual behavior

Perform any coding task which uses a decent number of tokens where the conversation is a few screens long.
Once scroll comes into play, the screen jumps automatically.
Meaning I'm never at the end of the conversation where I have typed new instructions. The box to type in prompt stays stationary, but the rest of the window (LLM response) jumps up and down. Making it almost impossible for me to read what the LLM had to say to my last prompt.
The jumping happens every time you scroll past a complete response of the LLM.
The down arrow button to take you to the end of the chat also does not bring you to the end of the chat in such scenarios.

Screenshots, recordings, or sanitized logs

No response

Safety check
  • I removed credentials and private project information from this report.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.