desktop: Home hides subdirectory sessions and mixes unrelated global projects
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Aptitud para principiantes
- 70/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
Línea de trabajo
Start with the two files the report names: home/sessions/records.ts (the pathKey exact-match filter) and home/sessions/controller.tsx (directories(project), which merges project.worktree with project.sandboxes). Reproduce via the local session and worktree APIs, then make matching segment-aware for the selected project while excluding unrelated entries from a shared global inventory, preserving Git worktrees and nested projects. Done when the child session appears under its project and the non-Git project no longer lists unrelated conversations.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Description
Summary
The Desktop Home project filter can both hide sessions whose working directory is a normal subdirectory of the selected project and display sessions from an unrelated project when the selected non-Git project uses a shared global worktree inventory.
This makes existing conversations appear lost and undermines separation between work and personal projects. The affected session metadata and messages remain available through the local API.
Environment
- opencode version:
opencode v2.3.0(verified on the reporting machine). The same symptoms were previously observed on Desktop 2.2.5. - OS: Windows 11,
Microsoft Windows NT 10.0.26200.0, x64. - Terminal: Desktop UI; diagnostic shell has
TERM=xterm-256color;TERM_PROGRAMandCOLORTERMare unset. - Shell: PowerShell 7.6.2;
ComSpec=C:\WINDOWS\system32\cmd.exe. - Install/channel: packaged Windows Desktop, standard release installation. No prerelease suffix in the reported version; the exact updater channel was not independently verified.
- Active plugins: configured globally:
opencode-supermemory,opencode-firecrawl,opencode-tavily,opencode-daytona,opencode-background-agents,opencode-vibeguard,opencode-notificator, and a localwhatsapp-notify.tsplugin. This lists configuration, not independently verified plugin runtime state. A plugin-disabled/clean-profile reproduction has not been performed.
Reproduction
The following paths and names are sanitized examples, not the reporter's real project data.
A. A child-directory session disappears from its own project filter
- Add an existing Git project at
C:\work\personal. - Create a conversation whose working directory is
C:\work\personal\android-app. - Verify that the session still has the personal project's
projectID, is not archived, and has readable message history. - Open Home and select the personal project.
- Observe that a root-directory session is listed, but the normal child-directory session is omitted.
The real affected Android-app session was confirmed through the session API with the correct project ID, a child working directory, and readable history. The corresponding folder and APK were also still present.
B. A shared global worktree inventory mixes unrelated projects
-
Have a non-Git project rooted at
C:\work\workrepresented byid: "global", plus a separate Git project atC:\work\personal. -
Reach a saved inventory state in which
GET /api/worktree?projectID=globalreturns both directories:[ {"directory":"C:\\work\\personal"}, {"directory":"C:\\work\\work"} ] -
Have separate root-directory conversations for those projects.
-
In Home, select the non-Git work project.
-
Observe personal conversations appearing in the work project's list.
The inventory state above was observed through the local API. The precise minimal sequence that first populated the shared inventory with both directories has not been isolated.
Expected Behavior
- Selecting a project should include its own ordinary subdirectory sessions, not only sessions whose directory exactly equals a root/worktree path.
- Selecting a non-Git project should not implicitly include every unrelated directory present in a shared
globalinventory. - Separately added nested projects and normal Git worktrees should retain their correct grouping.
- Showing a conversation should not require changing its working directory or moving its files.
Actual Behavior
- The Android-app conversation was absent from the personal Home list even though its session, project association, files, and messages still existed.
- The non-Git work project's Home list included personal conversations.
- There was no API deletion or archive operation associated with the missing conversation.
The shipped 2.3.0 renderer source map contains this exact-match filter in home/sessions/records.ts:
const selected = input.projectDirectories()
const directories = selected ? new Set(selected.map(pathKey)) : undefined
const sessions = directories
? input.sessions().filter((session) => directories.has(pathKey(session.location.directory)))
: input.sessions()
The corresponding helper in home/sessions/controller.tsx returns:
function directories(project: LocalProject) {
return [project.worktree, ...(project.sandboxes ?? [])]
}
The exact-match filter excludes ordinary child directories. When a shared global inventory supplies unrelated entries as sandboxes, returning all of them also allows cross-project root-directory matches.
Additional Context
- Both symptoms were observed on this installation before applying a local workaround. They reappeared after upgrading from 2.2.5 to 2.3.0, which replaced the locally modified renderer with the official one. This is not a request for the updater to preserve unsupported package modifications.
- A local renderer-only workaround limits a global selection to its selected canonical directory and allows segment-aware descendant matching for the selected project's own sessions, while excluding separately added nested projects and preserving Git worktree behavior.
- The workaround was tested against extracted packaged functions: 21 regression checks passed, including the real child session metadata; six additional repair-tool safety checks passed.
- After applying it, the Android-app session was observed in the personal Home UI tree. The final 2.3.0 work-project UI verification was interrupted by the machine locking and is not claimed as completed. Earlier 2.2.5 verification had confirmed the analogous work-child conversation visible and separate from personal conversations.
- Session IDs, project associations, parent relationships, and working directories were not changed by the workaround. Local checks preserved all 145 inventoried sessions, all preexisting messages in the two specifically checked conversations, and all 101 checked project files.
- A local workaround is not a durable fix because an official application update replaces the renderer. Please address the filtering/grouping behavior upstream.
- No private conversation content, account credentials, full user configuration, or private screenshots are attached.
Plugins
opencode-supermemory; opencode-firecrawl; opencode-tavily; opencode-daytona; opencode-background-agents; opencode-vibeguard; opencode-notificator; local whatsapp-notify.ts (configured; not independently isolated)
OpenCode version
2.3.0 (also observed on 2.2.5)
Steps to reproduce
The following paths and names are sanitized examples, not the reporter's real project data.
A. A child-directory session disappears from its own project filter
- Add an existing Git project at
C:\work\personal. - Create a conversation whose working directory is
C:\work\personal\android-app. - Verify that the session still has the personal project's
projectID, is not archived, and has readable message history. - Open Home and select the personal project.
- Observe that a root-directory session is listed, but the normal child-directory session is omitted.
The real affected Android-app session was confirmed through the session API with the correct project ID, a child working directory, and readable history. The corresponding folder and APK were also still present.
B. A shared global worktree inventory mixes unrelated projects
-
Have a non-Git project rooted at
C:\work\workrepresented byid: "global", plus a separate Git project atC:\work\personal. -
Reach a saved inventory state in which
GET /api/worktree?projectID=globalreturns both directories:[ {"directory":"C:\\work\\personal"}, {"directory":"C:\\work\\work"} ] -
Have separate root-directory conversations for those projects.
-
In Home, select the non-Git work project.
-
Observe personal conversations appearing in the work project's list.
The inventory state above was observed through the local API. The precise minimal sequence that first populated the shared inventory with both directories has not been isolated.
Screenshot
No response
Operating System
Windows 11 x64, Windows NT 10.0.26200.0
Terminal
OpenCode Desktop; diagnostics from PowerShell 7.6.2 (TERM=xterm-256color)
- Lenguaje dominante
- TypeScript
- Estrellas
- 227k
- Forks
- 30.7k
- Merge medio
- 3 h 57 min
- PR fusionados (30 d)
- 484
Preparar el entorno
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de anomalyco/opencode
-
[Site] Active section detection should respect scroll-margin-topPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertoarea/web reproduced type/bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
anomalyco/opencode#65384 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/cli type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#65379 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Shell tool: no upper bound on the timeout a model can ask for, so one call can hold a turn for hoursAbiertoarea/core platform/linux type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
anomalyco/opencode#65254 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
inference/go type/feature
Dificultad 1/5 1-3 horas Aptitud para principiantes 72/100
anomalyco/opencode#65148 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area/providers type/feature version/v2
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
anomalyco/opencode#64845 · 1 comentario ·
Los mantenedores suelen responder en 1 día
Todos los issues de anomalyco/opencode
Issues similares
-
[Provider] antigravity-acp catalog omits gemini-4-hydrogen and gemini-4-neon that agy acp offersPosiblemente ocupada Un pull request vinculado a esta issue está abierto o ya se fusionó. Abiertocatalog provider provider-compatibility
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
lidge-jun/opencodex#9037 · 1 comentario · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
Project submission: xmcp DocsAbierto
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
slavakurilyak/awesome-ai-agents#1005 ·
-
kind/bug triage/unresolved
Dificultad 2/5 1-3 horas Aptitud para principiantes 60/100
Los mantenedores suelen responder en 1 día
-
effort:S P3 refactor
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
nightscout/nocturne#3735 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
wpilibsuite/systemcore-blocks-interface#641 ·
Los mantenedores suelen responder en 2 días