Repository navigation
OpenCode Desktop: Old project that has the same name conflicts with new/current folder. OC trying to access the old folder #53686
Description
Activity
Thanks for the clear write-up, @sspilleman!
You're on OpenCode 1.18.35, which is v1. v1 now only gets fixes for critical problems (data loss, security issues, crashes or breakage with no workaround), so this one is unlikely to be fixed there. Other v1 issues already describe the same stale-path and project-removal behaviour, e.g. #48349 and #49476.
We'd encourage you to try OpenCode v2 (the
@opencode/clipackage,opencode2command), which is where active development happens. If you think this is critical, or you see the same problem on v2, please reply here with the details.
This issue might be a duplicate of existing issues. Please check:
- Bug Report: OpenCode Desktop Opens Same-Named Projects Incorrectly #42554: Desktop opens the previously accessed project when two projects have the same folder name.
- [Bug] Desktop: removing a project does not purge cache, re-adding resurrects stale path #47803: Removing and re-adding a project at its new location resurrects the stale path.
- [BUG] Unable to add project in different path with same project name #40963: Adding a project at a different path fails when it has the same project name.
- Opening a folder with the same name in different project directories navigates to the previously opened project #42284: Opening same-named folders in different project directories navigates to the previously opened project.
Thanks for the clear write-up, @sspilleman!
You're on OpenCode 1.18.35, which is v1. v1 now only gets fixes for critical problems (data loss, security issues, crashes or breakage with no workaround), so this one is unlikely to be fixed there. Other v1 issues already describe the same stale-path and project-removal behaviour, e.g. #48349 and #49476.
We'd encourage you to try OpenCode v2 (the
@opencode/clipackage,opencode2command), which is where active development happens. If you think this is critical, or you see the same problem on v2, please reply here with the details.I'm on latest according to Homebrew: /opt/homebrew/Caskroom/opencode-desktop/1.18.34 (428.8MB)
Thanks for checking, @sspilleman. The Homebrew
opencode-desktopcask (1.18.34) is the newest v1 release, but it's still v1. OpenCode v2 is a separate install (the@opencode/clipackage,opencode2command), so it doesn't arrive as a Homebrew update to that cask.v1 only gets fixes for critical problems. A stale project path after moving a folder doesn't meet that bar, so this won't be fixed in v1 and I'm closing the issue. The same behaviour is also tracked in #48349 and #49476. We'd encourage you to try v2, which is where active development happens.
Description
I have a project called 'bun'. Initially it was in the the folder /opt/Nextcloud/bun, and I added it as a project in OpenCode (Desktop). After I ditched Nexcloud, the new project folder is /opt/bun. I closed the old project in the project tree. I then added the project from /opt/bun (so it has the same name). Somehow OC kept the original path in memory giving errors (obviously, as the original folder location doesn't exist any more).
I was hesitating wether to file it as a feature request, because closing a project in the tree doesn't delete is, so the feature request then would be to add a feature to actually delete a project from OC.
I decided on bug report, as it didn't provide any error or warning in the UI. I had to dig through the log files to find out OC was still trying tho access the old directory, resulting in FileNotExists exceptions.
Plugins
No response
OpenCode version
1.18.35 (1.18.35)
Steps to reproduce
No response
Screenshot and/or share link
No response
Operating System
macOS Tahoe 26.7 (25G229)
Terminal
macOS terminal, but not relevant, I used OC Desktop