session list dialog empty #57068

Activity

1. opencode-agent commented on Oct 19, 2026

   

   opencode-agentBot

   on Oct 19, 2026 – with OpenCode Agent

   Contributor

   More actions

   Thanks for the detailed report! I think this is a duplicate of #49827. After a V1→V2 upgrade, the migrated sessions are still in the database (so the API and ctrl+O show them), but the project-scoped session list (<leader>l) filters them out. This happens because the importer leaves them attached to V1's catch-all global project, or with an empty (NULL) path, instead of the project V2 creates for your folder.

   Possible duplicates and closely related issues, ordered by likelihood:

   • migrate-v1: non-git sessions in "global" project hidden after V1→V2 upgrade #49827: V1 sessions from folders that aren't git repos stay in the global project and are hidden from the session picker after upgrading; the rest of the history is still reachable via ctrl+O
   • V1→V2 importer keeps project_id='global' for non-git directories, so migrated sessions never appear in the per-directory session picker #50551: same root cause, with an analysis of the importer keeping project_id='global'
   • session: v1 "global" sessions stay unattributed after migration and are hidden from v2's session list #51176: V1 global sessions stay unattributed after migration and are hidden from V2's session list
   • cli: migrated v1 sessions from non-git dirs missing from session list #52919: migrated V1 sessions from folders that aren't git repos are missing from the session list; the workaround there is ctrl+O or opencode -s <sessionID>
   • sessions: V1 sessions from non-git directories hidden from the project session list #53450: same symptom, with notes on reassigning the project as a manual workaround
   • v2: sessions with path=NULL (around v1's add_session_path schema change) are missing from project session lists #51144: if your workspace is a git repo, this is the more likely match: sessions whose path was migrated as NULL are left out of the project session list even though their project is correct

   The proposed fixes are in #51935 and #51514. In the meantime, ctrl+O (as you found) or opencode -s <sessionID> still opens the older sessions.

   The bot will close this issue as a duplicate in 1 day unless you reply explaining how your problem is different.
2. opencode-agent

   added

   pending close

   triaging

   on Oct 19, 2026
3. opencode-agent

   closed this as duplicateon Oct 20, 2026
4. opencode-agent commented on Oct 20, 2026

   

   opencode-agentBot

   on Oct 20, 2026 – with OpenCode Agent

   Contributor

   More actions

   We haven't heard back in a day, so I'm closing this as a duplicate of #49827. In both, migrated V1 sessions are still in the database and reachable via ctrl+O, but the project-scoped session list (<leader>l) hides them. Please follow #49827 for updates. If your workspace is a git repo, #51144 (sessions migrated with a NULL path) may be the closer match. Until a fix lands, ctrl+O or opencode -s <sessionID> still opens your older sessions. If your problem turns out to be different, reply here and explain how, and we can reopen this. Thanks for the report!