Cursor CLI appears to retain the full session history instead of keeping a bounded working history window. In long-running sessions, this triggers frequent tmux refreshes/repaints and makes the CLI feel noisy and less responsive.
Claude handles this better by maintaining a limited history length rather than continuously carrying the full history forward.
Requested behavior:
Keep only a bounded amount of active CLI history for rendering/interaction.
Reduce unnecessary tmux refreshes or full-pane repaints caused by large retained history.
Optionally expose a configurable history/window size for advanced users.
Why this matters:
Improves responsiveness in long-running CLI sessions.
Reduces tmux redraw/refresh churn.
Brings Cursor CLI behavior closer to Claude’s more stable history management.
We are tracking some issues around flickering when running on tmux. Wondering if the symptoms are the same on your side? If it’s different, a screen recording would be really useful!
Thanks for the reply! I cannot share my screen recording due to company’s data privacy policy. Here are the steps to reproduce:
Have a long history CLI like 10k lines. When scrolling a tmux window in the visual mode, we can check the history length.
We leave that tmux window for a long time (properly 10 mins - 1 hour) and work with another agent CLI.
We come back to this tmux window, then we observe that the window automatically scrolls from top (oldest) to down (latest). When the history is long, this scrolling top down behavior can last 30 seconds. This behavior can also be triggered by other events, but since they are quite random, I am not sure about the specific pattern.