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
Unable to access active / old sessions / projects at all when accessing WebUI at the same served url on two different browsers.
Plugins
None
OpenCode version
1.18.28 (WebUI)
Steps to reproduce
Run opencode web --port 4096 --hostname 127.0.0.1. I run it on cloud server (Ubuntu 24.04.4 LTS)
Access http://127.0.0.1:4096/ on a browser, start a new session. I ssh port forward to my Windows 11 Home PC and access it there.
Now http://127.0.0.1:4096/ on a different browser (not sharing the localcache), see there is no way to load the active / previous sessions / projects!
Related Bug: At step 2: go to Home and see it never gets populated of any sessions whatsoever!
Screenshot and/or share link
Image from the browser that I am actively running the sessions. Notice:
Three sessions running as different tabs.
Home is never populated.
Image from a different browser at the exact same URL.
Operating System
Ubuntu 24.04.4 LTS -> port forwarded -> Windows 11
If your issue is specifically about accessing the UI from a different browser (not sharing localStorage), it aligns most closely with #45011, which has a detailed root-cause analysis and a workaround.
Activity
[-]WebUI not populating sessions[/-][+]WebUI not populating sessions / projects[/+]github-actions commentedon Sep 10, 2026
This issue might be a duplicate of existing issues. Please check:
opencode webon a remote/headless server accessed via port forwarding, with sessions not appearing despite the API returning them correctly./api/sessionreturns sessions correctly.If your issue is specifically about accessing the UI from a different browser (not sharing localStorage), it aligns most closely with #45011, which has a detailed root-cause analysis and a workaround.