Add configurable scrollback/message limit to reduce TUI lag #9930

Activity

1. github-actions

   assigned

   rekram1-node

   on Jan 22, 2026
2. github-actions

   added

   opentuiThis relates to changes in v1.0, now that opencode uses opentuiThis relates to changes in v1.0, now that opencode uses opentui

   perfIndicates a performance issue or need for optimizationIndicates a performance issue or need for optimization

   on Jan 22, 2026
3. github-actions commented on Jan 22, 2026

   

   github-actionsBot

   on Jan 22, 2026 – with GitHub Actions

   Contributor

   More actions

   This issue might be a duplicate of existing issues. Please check:

   • [BUG] Cannot scroll to beginning of long conversations (message limit hardcoded to 100) (#6138) #6137: Cannot scroll to beginning of long conversations (message limit hardcoded to 100) - directly addresses configurable message_limit in tui config
   • [FEATURE]: Paginated message loading for long sessions #6548: feat: virtualized scrolling + paginated message loading for long sessions - proposes virtualized rendering as a long-term solution for large histories
   • feature request: pagination for messages & sessions #4918: feature request: pagination for messages & sessions - requests pagination and message limits to prevent lag in long sessions
   • High CPU usage (100%+) during LLM streaming in long sessions due to O(n) text buffer rendering #6172: High CPU usage (100%+) during LLM streaming in long sessions due to O(n) text buffer rendering - identifies the underlying performance issue causing lag
   • [FEATURE]: TUI whole and LSP memory limits as part of configuration #8947: [FEATURE]: TUI whole and LSP memory limits as part of configuration - requests memory constraints configuration to address memory/performance issues

   Feel free to ignore if none of these address your specific case.
4. github-actions commented on Mar 28, 2026

   

   github-actionsBot

   on Mar 28, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 90 days of no activity. If the issue is still relevant please open a new one.
5. github-actions

   closed this as completedon Mar 28, 2026