[Desktop][macOS] Sidebar infinite loading spinner in both Codex and Work
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using (From “About Codex” dialog)?
26.901.51231 (build 8109)
What subscription do you have?
pro
What platform is your computer?
macOS 26.5.2 (25F84)
What issue are you seeing?
The loading spinner at the bottom of the sidebar never disappears.
This reproduces in both:
- Codex
- Work
The rest of the application remains functional. I can open and create chats.
Restarting the app and upgrading to a newer build did not resolve it.
The network connection is working normally.
What steps can reproduce the bug?
Feedback ID: 01a07557-75da-7421-9f10-8bca185f433b
What is the expected behavior?
Sidebar pagination should eventually finish, show additional entries, or display an explicit load error.
Additional information
- Thread listing succeeds and returns a full page of 50 items.
- No sidebar source or host is reported as unavailable.
- Relevant backend requests returned HTTP 200.
- Local SQLite integrity checks pass.
- Local history backfill status is
complete. - The client has a relatively large history:
- 782 indexed Codex threads
- 629 non-archived threads
- 572 visible non-archived threads
- approximately 2.0 GB of active session data
- approximately 1.1 GB of archived session data
This may be a pagination / hasNextPage state issue triggered by larger histories.
The current UI appears to keep rendering the spinner while hasNextPage remains
true, and load-more failures may not surface an error to the user.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the desktop sidebar pagination flow, especially the hasNextPage state and load-more failure handling described in the report. Reproduce with a large history and the supplied Feedback ID, then verify that pagination adds entries, stops the spinner, or surfaces an explicit error instead of loading indefinitely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos, rust
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 52/100