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
{{ message }}
Repository navigation
Historical sessions disappear - Expected a string starting with "ses", got "dummy" error #28486
Shell: PowerShell
Description:
After upgrading or running opencode, all historical sessions are no longer visible in the UI. The application still functions correctly for new sessions, but the session history is lost.
Error from log:
ERROR 2026-05-20T15:48:39 service=server error=Expected a string starting with "ses", got "dummy" cause=Error: Expected a string starting with "ses", got "dummy"
at (B:/~BUN/root/chunk-b1nng1ye.js:25:10123)
at (B:/~BUN/root/chunk-b1nng1ye.js:35:4256)
at (B:/~BUN/root/chunk-gx4g06p1.js:2:107948) {
[cause]: Error: Expected a string starting with "ses", got "dummy"
} failed
Additional Info:
Database file (opencode.db) is 63MB, suggesting data is still present
storage/session_diff/ contains 18 session files (from May 13-15)
New sessions are created successfully after the error
The error appears to be a session ID validation failure where "dummy" was found instead of a proper "ses_*" format
Expected Behavior:
Historical sessions should remain visible and accessible after upgrades/restarts.
Actual Behavior:
All historical sessions disappear from the UI, though the database file size indicates data is still present.
If your issue is the same root cause, consider adding a comment there instead. If the specific Expected a string starting with "ses", got "dummy" error is distinct from those issues, this report is still valuable — please add any additional reproduction details if possible.
seems still an issue here. I didn't upgrade recently, where should I investigate? Judging from the sqlite database size, the message data is still there.
EDIT: the message data is ok but the session table is empty now. Guess that's the reason.
Activity
github-actions commentedon May 20, 2026
This issue might be a duplicate of existing issues. Please check:
If your issue is the same root cause, consider adding a comment there instead. If the specific
Expected a string starting with "ses", got "dummy"error is distinct from those issues, this report is still valuable — please add any additional reproduction details if possible.HaleTom commentedon Jun 22, 2026
Also on Linux:
HaleTom commentedon Jun 22, 2026
Related:
--continue --fork: Expected a string starting with "ses", got "dummy" #29262 — TUI shows server error on--continue --fork: Expected a string starting with "ses", got "dummy" #29262github-actions commentedon Aug 22, 2026
To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
digglife commentedon Sep 19, 2026
seems still an issue here. I didn't upgrade recently, where should I investigate? Judging from the sqlite database size, the message data is still there.
EDIT: the message data is ok but the session table is empty now. Guess that's the reason.
sbe-arg commentedon Sep 22, 2026
i have the same problem when I empty the session list for a workspace