Home sessions hidden from /sessions in global project #29581

Activity

1. cagedbird043 commented on May 27, 2026

   

   cagedbird043

   on May 27, 2026

   Author

   More actions

   PR opened: #29582
2. github-actions

   assigned

   simonklee

   on May 27, 2026
3. Appjak34 commented on May 29, 2026

   

   Appjak34

   on May 29, 2026

   More actions

   Same bug confirmed on macOS with opencode 1.15.12. Here's the detailed root cause analysis from our debugging:

   Root cause: The TUI session filter function (W() in the Sync provider) returns {path: relativePath} or {scope: "project"}. Both are valid query params for GET /session (the Effect HTTP handler's QF schema includes scope: optional(Literals(["project"])) and path: optional(String)). The server uses these to filter sessions, but sessions with project_id = "global" and no path set (empty string) don't match any project.

   Why CLI works: opencode session list uses a different code path — the RPC handler listSessions(D) calls this.sdk.session.list({directory: D.cwd ?? void 0, roots: true}) directly against the DB with roots: true, bypassing the HTTP filter entirely.

   Database evidence from our env:

   • Sessions exist: project_id = 'global', directory = '/Users/appjak', path = null
   • No project with matching worktree in the project table
   • app.toggle.session_directory_filter toggles between {path: ""} and {scope: "project"} — neither helps because both paths end up filtering out global sessions

   Suggested fix: The W() function should fall back to {directory: instance.directory, roots: true} when no project matches the current directory, mirroring the CLI behavior. Alternatively, the server-side handler for GET /session should include project_id = 'global' sessions when scope: 'project' finds no matching project.
4. hxrikp1729 commented on Jun 2, 2026

   

   hxrikp1729

   on Jun 2, 2026

   More actions

   Hitting this on a non-home directory as well — adding evidence in case it helps broaden the fix.

   Setup

   • OpenCode 1.15.6 on macOS (anomalyco fork)
   • Working dir: a subfolder of ~/Desktop (not $HOME)
   • Project worktree: / (global)

   Symptom

   23 of 62 sessions in this directory are invisible in /sessions. opencode session list and opencode -s <id> both find them fine.

   Root cause: writer/reader contract mismatch on session.path

   Two states exist for the path column on sessions in the same directory:

   path value	Count	Visible in /sessions?
   NULL	39	yes
   '' (empty string)	23	no

   All 23 invisible sessions were created on OpenCode ≥ 1.14.39 (oldest 2026-05-06). All 39 visible ones are on ≤ 1.14.28. Something between those releases changed session creation from writing NULL to writing ''.

   The server-side filter at packages/opencode/src/session/session.ts:1058:

   input.directory
     ? or(...conds, and(isNull(SessionTable.path), eq(SessionTable.directory, input.directory))!)!
     : or(...conds)!,

   The fallback that catches "no path-prefix match" only fires for path IS NULL. Sessions with path = '' don't match either branch and get filtered out.

   Why this is broader than the home-directory case

   PR #29582 special-cases the home directory by switching to project scope. That only triggers when the worktree resolves to / and the directory is $HOME. My case is a Desktop subfolder, so #29582 wouldn't fix it — but the underlying bug is identical.

   Proposed minimal fix (server-side, one line)

   // session.ts:1058
   - and(isNull(SessionTable.path), eq(SessionTable.directory, input.directory))!
   + and(or(isNull(SessionTable.path), eq(SessionTable.path, ''))!, eq(SessionTable.directory, input.directory))!

   This is non-breaking and covers existing DBs without requiring a data migration. Alternatively (or additionally), normalize at the writer to always store NULL when no path applies.

   Local workaround (no app restart of fix, just data normalization)

   UPDATE session SET path = NULL WHERE path = '';

   Confirmed on my DB: the 23 hidden sessions reappeared after restarting the TUI.
5. github-actions commented on Aug 2, 2026

   

   github-actionsBot

   on Aug 2, 2026 – with GitHub Actions

   Contributor

   More actions

   To stay organized issues are automatically closed after 60 days of no activity. If the issue is still relevant please open a new one.
6. github-actions

   closed this as not plannedon Aug 2, 2026