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
[Bug] Web UI: Sessions fail to save/persist for secondary projects in multi-workspace (Windows) #19672
When running OpenCode in Web mode on Windows and using the multi-workspace feature (having multiple projects open in the left sidebar), session persistence completely breaks for the secondary projects.
Sessions created in the first loaded project save to the database and work correctly. However, if a second project is added/opened, any "New session" created for this second project exists only temporarily in the UI. It fails to persist in the database, never appears in the sidebar history, and attempting to rename it fails silently (it just reverts to the original name).
Plugins
oh-my-opencode ; @whisperopencode/push
OpenCode version
1.3.5
Steps to reproduce
Steps to reproduce the behavior:
Start OpenCode via CLI on Windows using: opencode web (e.g., inside a parent folder or directly selecting projects).
Open the Web UI at http://localhost:.......
Open/Select "Project A". Create a session -> It saves correctly in the sidebar.
Add/Open a second project "Project B" from the Web UI sidebar.
Switch to "Project B" and click on "New session".
Type a prompt.
Notice that the session is NOT saved in the left sidebar history for Project B.
Click the ... menu and try to rename the session -> The rename fails silently and the session remains unsaved.
Expected behavior
Sessions for any project opened in the Web UI should properly save to the local opencode.db and immediately appear in their respective sidebar history, regardless of whether it is the first or second project loaded in the workspace
I found the root cause: it's a path separator issue between Windows () and the Web/Mobile UI (/). The SQLite database stores the directory with backslashes, but the frontend queries it with forward slashes. A strict string comparison fails. The backend needs to normalize paths (e.g., using Node's path.normalize()) before querying the DB.
Activity
github-actions commentedon Mar 29, 2026
This issue might be a duplicate of existing issues. Please check:
chpeu commentedon Mar 31, 2026
I found the root cause: it's a path separator issue between Windows () and the Web/Mobile UI (/). The SQLite database stores the directory with backslashes, but the frontend queries it with forward slashes. A strict string comparison fails. The backend needs to normalize paths (e.g., using Node's path.normalize()) before querying the DB.
github-actions commentedon Jul 3, 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.