You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
never rm -rf unknown dirs by default or without asking
protect bind mounts/external dirs
make cleanup opt-in (env flag) or dry-run first?
aks user if they wanna add the new detected folder as a repo
I don't understand why a Docker named volume is the default for project directories, since it's impractical for common development workflows where you need to test locally on the host before committing; I had to add my project folder first via UI and then bind-mount ~/workspaces:/workspace.
Good findings! I guess this was done to support container installs.
To support local and container maybe we could go with something like:
Mount detection: Use stat to check if a directory's device differs from the repos base directory (bind mounts = different device). Mounted dirs get protection.
Two-tier cleanup:
Internal-created (same filesystem, OpenCode-owned): Safe to clean
External-mounted (different filesystem, user-owned): Never touch
Opt-in required: Disable all cleanup by default. Users who want automatic cleanup (contained installs) explicitly enable it.
Yes, I believe this was before the File management and file browser. I just decided to remove it all together. Doesn't make a whole lot of sense. The user could always go in and browse the workspace and clean up any directories.
Activity
fix: remove automatic orphaned directory cleanup on startup (#128)
fix: remove automatic orphaned directory cleanup on startup (#128) (#132
theepicsaxguy commentedon Feb 14, 2026
Good findings! I guess this was done to support container installs.
To support local and container maybe we could go with something like:
Mount detection: Use stat to check if a directory's device differs from the repos base directory (bind mounts = different device). Mounted dirs get protection.
Two-tier cleanup:
Internal-created (same filesystem, OpenCode-owned): Safe to clean
External-mounted (different filesystem, user-owned): Never touch
Opt-in required: Disable all cleanup by default. Users who want automatic cleanup (contained installs) explicitly enable it.
chriswritescode-dev commentedon Feb 14, 2026
Yes, I believe this was before the File management and file browser. I just decided to remove it all together. Doesn't make a whole lot of sense. The user could always go in and browse the workspace and clean up any directories.
chriswritescode-dev commentedon Mar 21, 2026
#161 - resolved , new method of use added
fix: remove automatic orphaned directory cleanup on startup (chriswri…