[Desktop] "Load more" button on sidebar behaves unpredictably

[shanebishop1]

load_more_bug.mov

Description

The "Load more" button is very flaky. There are two main issues I've noticed:

1. It is displayed to the user even if the project has no more sessions to load. It then remains clickable for an arbitrary amount of pagination.
2. If a project does have more valid pages of sessions to pull, the button sometimes exhibits what feel like no-ops, forcing the user to click multiple times. Then, even when the new sessions are pulled in, it isn't always the correct number (5) of sessions.

I believe this has to do with root session filtering and the /session endpoint returning sessions for directories that are not the same as the given project.

Plugins

No response

OpenCode version

1.1.19

Steps to reproduce

1. Create a new directory
2. Open that directory as a project in the desktop client
3. Observe that the project has a "Load more" button despite not having any more sessions to load
4. Click the button repeatedly for what initially appears to be a no-op

or

1. Open a pre-existing project in the desktop client (one that has many sessions/forks/subagents/etc.)
2. Click the "Load more" button
3. Observe that the button does not reliably add another 5 (the limit set for each page fetched) sessions to the sidebar view

Screenshot and/or share link

No response

Operating System

Sequoia 15.5

Terminal

No response

[github-actions]

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

• The sessions list seems to show all history, not the sessions history of the working directory #6098: The sessions list seems to show all history, not the sessions history of the working directory
• Sessions are now mixed with home directory session list, disregarding which directory you're in #3551: Sessions are now mixed with home directory session list, disregarding which directory you're in
• Sessions not displayed in /session for specific project path despite being written to storage #7186: Sessions not displayed in /session for specific project path despite being written to storage

These issues describe similar problems with session filtering by directory/project path, which aligns with your observation about 'root session filtering and the /session endpoint returning sessions for directories that are not the same as the given project.'

Feel free to ignore if none of these address your specific case.

[shanebishop1]

#8430 should address this