web: adding a new project for a dashed folder name falls back to "/" project
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 55/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- typescript
- Ambito
- frontend
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.0running as a systemd user service with noWorkingDirectory=, so the server process CWD is/) - Shell: /bin/fish
- Install/channel: release (official repo package)
- Active plugins: none configured
Reproduction
- Start the server:
opencode serve --port 4096 --hostname 0.0.0.0(e.g. systemd user unit; no WorkingDirectory set). - Create a new directory with a dash in the name:
mkdir ~/doom-scroller(tried both plain and aftergit init— same result). - Open the web UI and try to add
~/doom-scrolleras a new project. - Observe: the root project
/is added/activated instead; nodoom-scrollerproject entry is ever created inGET /api/project. - 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.tsxdoingconst 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 serveuses/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/projectexposes 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.
- Lingua principale
- TypeScript
- Stelle
- 225k
- Fork
- 30.4k
- Merge medio
- 4h 16m
- PR unite (30g)
- 528
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di anomalyco/opencode
-
reproduced
Difficoltà 2/5 1-3 ore Idoneità per principianti 61/100
anomalyco/opencode#62873 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
anomalyco/opencode#62822 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
anomalyco/opencode#62601 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
reproduced
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
anomalyco/opencode#62516 · 2 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
anomalyco/opencode#62374 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di anomalyco/opencode
Issue simili
-
code-quality good-first-issue
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
OpenRailAssociation/netzgrafik-editor-frontend#1481 ·
I maintainer di solito rispondono entro 1 giorno
-
🙌 icon request
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
lucide-icons/lucide#5183 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 81/100
cloudflare/capnweb#293 ·
I maintainer di solito rispondono entro 2 giorni
-
bug implicit-state
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
-
area:models enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno