You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When reopening a long session, the message timeline loads only a small batch of recent messages. Loading earlier history requires manually clicking "Load earlier messages" repeatedly. For sessions with significant history, this makes it hard to quickly get context on what was discussed.
Request: Either increase the default number of messages loaded on session open, or add a config option (e.g. history.initialLoad) to control it.
Use case: I have long-running sessions and want to scroll back through the full conversation without clicking "Load earlier messages" multiple times. All the data is already in the local SQLite DB — it's just a matter of how much the UI fetches upfront.
Possible approach:
Add a config key like "initialMessages": 200 (or "all")
Or simply increase the default batch size
Not requesting any changes to compaction or storage — the data is already retained. This is purely a UI/pagination concern.
No issue template was used. Feature requests must use the Feature Request template, which requires a verification checkbox confirming the feature hasn't been suggested before, and the title must start with [FEATURE]:.
Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
Activity
github-actions commentedon Apr 12, 2026
This issue doesn't fully meet our contributing guidelines.
What needs to be fixed:
[FEATURE]:.Please edit this issue to address the above within 2 hours, or it will be automatically closed.
This issue might be a duplicate of existing issues. Please check:
GET /session/:id/message— covers the API-level pagination needed to support configurable message load countsIf you believe this was flagged incorrectly, please let a maintainer know.
github-actions commentedon Apr 13, 2026
This issue has been automatically closed because it was not updated to meet our contributing guidelines within the 2-hour window.
Feel free to open a new issue that follows our issue templates.