web: adding a new project for a dashed folder name falls back to "/" project

Abierto
  • ¿Algo no está bien?
#62,776 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
55/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
frontend

Línea de trabajo

Start by reading packages/app/src/pages/session.tsx, which the issue identifies as decoding the dir URL parameter and falling back to the server directory. Trace how the web UI encodes and sends the selected project path, then check the related tests or add-project flow for coverage. Done when a dashed directory opens as its own project and no / project is created.

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

Descripción

Summary

Adding a brand-new project folder to the web UI via "new project" silently lands on the root / project instead of the requested directory. Reproduced with a folder whose name contains a dash (~/doom-scroller); an otherwise-identical no-dash control folder works on the first try. Impact: new projects with dashed names cannot be created from the web UI at all, and a stray / project is left behind that the API cannot delete.

Environment

  • opencode version: v2.2.5 (pacman package opencode 2.2.5-1.1, Arch/CachyOS official build)
  • OS: Linux 7.3.1-1-cachyos x86_64
  • Terminal: Browser web UI (served by opencode serve --port 4096 --hostname 0.0.0.0 running as a systemd user service with no WorkingDirectory=, so the server process CWD is /)
  • Shell: /bin/fish
  • Install/channel: release (official repo package)
  • Active plugins: none configured

Reproduction

  1. Start the server: opencode serve --port 4096 --hostname 0.0.0.0 (e.g. systemd user unit; no WorkingDirectory set).
  2. Create a new directory with a dash in the name: mkdir ~/doom-scroller (tried both plain and after git init — same result).
  3. Open the web UI and try to add ~/doom-scroller as a new project.
  4. Observe: the root project / is added/activated instead; no doom-scroller project entry is ever created in GET /api/project.
  5. Control: mkdir ~/Music (no dash, also not a git repo) and add via the same flow → works immediately, project entry created.

Expected Behavior

The web UI creates/opens a session on a project for the directory the user chose (/home/<user>/doom-scroller).

Actual Behavior

The root project / (the server process's CWD) is added/activated instead — one second after the server momentarily initialized the correct directory. The requested project never appears in the project picker.

Additional Context

Server journal (journalctl --user -u opencode-web) shows the correct path arriving, then a fallback one second later:

12:04:50 INFO spawning process { ... cwd: "/home/<user>/doom-scroller" }   # correct — UI sent the right path
12:04:51 INFO spawning process { ... cwd: "/" }                            # 1s later — fell back to server CWD
12:05:32 INFO spawning process { ... cwd: "/home/<user>/Music" }           # no-dash control — success

Suspected mechanism, matching previously reported issues:

  • #12918 identified packages/app/src/pages/session.tsx doing const projectDirectory = decode64(params.dir) ?? sdk.directory — when the base64 URL parameter fails to decode, it silently falls back to the server's base directory.
  • #14445 / #6336: opencode serve uses / as its base directory — which is exactly where this bug lands.
  • #18593 / #15719: other users report the same stray / "ghost" project in the picker; GET /api/project exposes only GET + PATCH (no delete), so it cannot be cleaned up via API either.

Frequency: consistent — failed on 3+ attempts with the dashed folder (git and non-git); the no-dash control succeeded on the first attempt every time. The dash is inferred from this A/B comparison (one dashed vs one no-dash folder); other special characters not tested.

Workaround that works reliably: start any session in the directory once from the CLI (cd ~/doom-scroller && opencode run "hi") — the project is registered server-side and immediately appears and works in the web UI picker.

Lenguaje dominante
TypeScript
Estrellas
225k
Forks
30.4k
Merge medio
4 h 16 min
PR fusionados (30 d)
528

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.