Skip to content

[Desktop] Sessions disappear from sidebar when creating new session - Windows v1.17.12 #34723

Closed

Description

@regerman78-ai

Description

Description

When I create a new session by clicking "Nueva sesión" in the sidebar, the previous session disappears from the list and cannot be recovered. The sessions are still stored in the database but not shown in the UI.

Environment

  • OpenCode Desktop version: v1.17.12
  • Operating System: Windows 10/11
  • Provider: OpenCode Zen (API Key)
  • Connected via: Google account

Steps to Reproduce

  1. Open OpenCode Desktop
  2. Start a conversation/session
  3. Click "Nueva sesión" (New session) in the sidebar
  4. Previous session disappears from the list
  5. Restart the app - sessions still don't appear

Expected Behavior

Previous sessions should remain visible in the sidebar and be accessible after creating a new session.

Actual Behavior

Sessions disappear from the sidebar. The database file at %USERPROFILE%\.local\share\opencode\opencode.db still contains the session data, but the UI doesn't display them.

Additional Context

  • Restarting the app doesn't fix the issue
  • The session data is not lost from the database, just not shown in the UI
  • This makes long-running conversations unreliable

Logs

  • Location: %LOCALAPPDATA%\ai.opencode.desktop\logs\opencode-desktop_*.log

Plugins

No response

OpenCode version

No response

Steps to reproduce

No response

Screenshot and/or share link

Image Image

Operating System

No response

Terminal

No response

Activity

  1. github-actions commented on Jul 1, 2026

    @github-actions
    Contributor

    This issue might be a duplicate of existing issues. Please check:

  2. DroveM3Crazy commented on Jul 2, 2026

    @DroveM3Crazy

    This has the same symptoms as #30374 — session list empty due to Windows path separator mismatch between storage (forward slashes) and queries (backslashes). PR #34806 normalizes all \directory\ comparisons to use forward slashes on Windows, which should resolve this. Could you test with the latest dev build once #34806 is merged and reopen if it persists?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions