Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

desktop: new-session project chip never reflects sibling directories of the same git repo

Abierto Apto para principiantes
  • ¿Algo no está bien?
#55,351 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
66/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
electron, typescript
Área
desktop

Línea de trabajo

El error está en el resolvedor de elementos seleccionados del compositor, que ejecuta list.find() con un OR de e.worktree === dir y e.sandboxes?.some(...). Empieza por el código del chip de proyecto y del desplegable en el renderer, y revisa el store de proyectos que fusiona los registros de GET /api/project en cada entrada de directorio. Está terminado cuando la etiqueta del chip y la marca de selección siguen al directorio hermano seleccionado, las coincidencias exactas se prueban antes del respaldo de sandboxes y el comportamiento de la barra lateral no cambia.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

reproduced
Description

The new-session project chip (first chip under the composer) never follows a directory selection for sibling directories of the same repository. It keeps showing the repository's canonical directory, and the checkmark in the dropdown stays on that same row, so switching between sibling clones looks like it silently failed.

It is UI-only: the click does update the draft's directory (verified in the desktop state store), and the session is created in the clicked directory, but the chip label and the checkmark never change. This makes it impossible to tell which directory a new session will run in.

Root cause, read from the shipped renderer bundle. GET /api/project returns one Project for all clones:

{"id":"7f3bb1b0…","canonical":"/home/me/work/app-dev","sandboxes":["/home/me/work/app-uat","/home/me/work/app-release"]}

The server-scoped projects store resolves each directory entry as {...projectRecord, ...directoryEntry}, so every sibling directory entry carries the same sandboxes array. The composer's selected-item resolver then does one find() over both predicates:

list.find(e => e.worktree === dir || e.sandboxes?.some(s => s === dir))

For dir = .../app-uat, the first entry (app-dev, whose hydrated sandboxes contains app-uat) matches the second predicate, so find() returns it before the exact-match entry is ever considered. The chip label and the checkmark are both derived from that resolver.

Suggested fix: exact match first, sandboxes only as a fallback:

list.find(e => e.worktree === dir) ?? list.find(e => e.sandboxes?.some(s => s === dir))

The sidebar project rows are unaffected, because they compare the selected directory exactly.

Plugins

@tarquinen/opencode-dcp, @maximtop/opencode-session-namer, @prevalentware/opencode-goal-plugin, opencode-tui-usage

OpenCode version

v2.0.28

Steps to reproduce
  1. Clone the same git remote into three independent directories (e.g. app-dev, app-uat, app-release) — three plain clones, not worktrees, so they all resolve to the same project ID.
  2. Add all three directories as projects in OpenCode Desktop.
  3. Start a new session in one of the non-canonical clones (e.g. app-uat).
  4. Open the project chip dropdown under the composer. The chip and the checkmark both stay on app-dev.
  5. Select app-release. Still app-dev.

The click itself works: after selecting app-uat, the draft's directory in ~/.config/ai.opencode.desktop/drafts.sqlite becomes .../app-uat and lastProject follows, and GET /api/location?location[directory]=.../app-uat returns project.canonical = .../app-uat. Only the chip label and the checkmark are stale.

Reproducible every time for any repository that has more than one of its directories added as a project (I hit it with three clones of one repo).

Screenshot and/or share link

A 12s screen recording of the dropdown (checkmark stuck on the canonical directory while the draft directory is a sibling clone) is available on request.

Operating System

Linux 6.6.155-amd64-desktop-hwe (x86_64), Deepin desktop, X11

Terminal

OpenCode Desktop (Electron app), no terminal attached

Lenguaje dominante
TypeScript
Estrellas
213k
Forks
28.4k
Merge medio
8 h 51 min
PR fusionados (30 d)
289

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de anomalyco/opencode

Todos los issues de anomalyco/opencode

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.