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
Session tab preview shows the same project name for every tab, ignoring the session's directory #51740
Hovering a session tab in the desktop app shows the same project name on every tab, regardless of which directory that session is actually in. The path line in the same card is correct.
A session in directory A, a session in directory B, and a session in the project actually named HomeServer all display the project name HomeServer. Only the path line differs between them.
No project has a custom name set (all 24 rows in the project table have name IS NULL), and displayName() falls back to getFilename(project.worktree) (packages/app/src/pages/layout/helpers.ts:49), so this is projectForSession() resolving to the wrong project rather than a stale name.
Every session in my database has project_id = 'global', and the project table has a row with id = 'global', worktree = '/', vcs = NULL, and zero project_directory rows. projectForSession() (packages/app/src/pages/layout/helpers.ts:96) returns byID.get(session.projectID) immediately and only matches on session.directory if that lookup misses:
Since every session carries project_id = 'global', the ID path always wins and the directory is never consulted. Note this is a display-only symptom for me, unlike #39667 where sessions were actually reassigned server-side.
I checked for the .git/opencode anchor file described in #39667 and it is absent from all six affected directories, so that particular cause does not apply here.
Steps to reproduce
Configure several projects, start sessions in at least two of them
Open a session tab's preview (hover and hold ~2s)
Observe the project name is identical across tabs while the path line differs correctly
Activity
github-actions commentedon Sep 28, 2026
Thanks for updating the issue with the bug description, reproduction steps, and system details!
thdxr commentedon Oct 11, 2026
Thanks for the report! OpenCode 2.0 is now out and development is focused on V2, so we're closing issues filed against OpenCode 1. Please upgrade (
opencode upgrade --major, details: https://anoma.ly/notes/opencode-2-0), and if this is still relevant on 2.0, reopen this issue or open a new one with your 2.0 version.— from 𝕺𝖕𝖊𝖓𝕮𝖔𝖉𝖊