opencode
opencode copied to clipboard
[BUG] Unable to Load Old Sessions
Description
Unable to load in old sessions. Has been a persistent issue since v1.0.2 for me.
Also experiencing the issue in my Docker container.
Those having issues might try disabling auto-update, then rolling back to v0.15.23.
OpenCode version
1.0.2 -> 1.0.23
Steps to reproduce
- Launch Opencode
- Use /session command
- Select Session
- Wait to Load
- Conversation history flashes and disappears
Screenshot and/or share link
https://github.com/user-attachments/assets/7af5fa66-0b02-4017-b217-25c138f40afa
Operating System
macOS 26.0.1 / Debian Docker Container
Terminal
VS Code + Ghostty
This issue might be a duplicate of existing issues. Please check:
- #3026: Same issue with sessions showing empty despite existing in storage after version upgrades (specifically affects v0.14.4+ with sessions from v0.13.x)
- #2987: Sessions disappearing/being lost entirely after using /compact command
- #2046: General "Failed to Open Session" error affecting session loading
The symptoms described (conversation history flashing and disappearing when loading old sessions) closely match the session loading issues reported in these other tickets. #3026 is particularly relevant as it identifies the specific version compatibility issue with session loading after API changes.
Feel free to ignore if none of these address your specific case.
Yes, it did look like an old bug that reappeared.
Does it reappear when you scroll up and down?
No, but I can continue the chat and the context appears to still be there. Seems like a rendering issue.
having this issue as well, however it doesnt load any session at all
running into this too 👍🏽
running into this too 👍🏽
I rolled back to v0.15.23 (latest available on brew) and things are working fine again.
can you give it another try when you have a moment?
Working for me now!
Not working for me, still the same. 😅
@reowens make sure you're on the latest version and perhaps try cleaning storage for opencode as well.
Also having the same issue
should be good now