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
{{ message }}
Repository navigation
Repo deletion causes misleading error alert; propose graceful handling of at least deleted worktrees #2679
When using git worktree with Fork, deleting a worktree and then switching back to Fork triggers a large, blocking error alert in the app:
Unexpected error:
open object db '/Users/is/work/proj/.git/worktrees/proj.docs'
open '/Users/is/work/proj/.git/worktrees/proj.docs/objects'. Path does not exist
Please contact Fork support
This is incorrect and misleading. Worktrees are transient by design — they are temporary working directories that developers routinely create and delete as part of normal Git workflows (feature branches).
Fork should not treat a missing worktree as a critical error that requires user action or support intervention. Instead, it should:
Silently ignore missing worktree paths when refreshing the repository state.
Automatically prune stale worktree references from its internals.
Never display a full‑screen alert with a "contact support" message for this scenario.
Personally I think this should work for any cloned repo (not necessarily a worktree); but for worktrees it's especially critical.
I updated to 2.69.0, opened a fresh worktree in Fork, then deleted it in terminal (using worktrunk: wt remove). Fork immediately crashed without any message. When I reopened it, this message appeared:
Tried 2.69.1: it didn't crash but the behaviour was still odd:
I created a worktree (wt switch -c test)
I ran fork /path/to/worktree
In Fork, it appeared as a new tab alongside the other tabs (so far so good)
I ran cd /path/to/worktree and wt remove
In Fork, the error message appeared:
When I clicked 'Close', the tab moved to a new Fork window (?): I ended up with two Fork windows, one with my normal tabs and one dedicated to the now-gone worktree (switchable with Cmd-`)
Activity
DanPristupov commentedon Jul 25, 2026
Do you use the latest 2.69.0?
IlyaSemenov commentedon Jul 26, 2026
No, I'm using what's told to be the latest version:
DanPristupov commentedon Jul 26, 2026
You switched Fork to the stable update channel. You need to wait for a stable release.
IlyaSemenov commentedon Jul 26, 2026
I updated to 2.69.0, opened a fresh worktree in Fork, then deleted it in terminal (using worktrunk:
wt remove). Fork immediately crashed without any message. When I reopened it, this message appeared:I am attaching the crash report:
Details
DanPristupov commentedon Jul 26, 2026
Can you try this build?
https://cdn.fork.dev/mac/Fork-2.69.1.dmg
IlyaSemenov commentedon Jul 26, 2026
Tried 2.69.1: it didn't crash but the behaviour was still odd:
wt switch -c test)fork /path/to/worktreecd /path/to/worktreeandwt removeIlyaSemenov commentedon Jul 26, 2026
Off-topic: it also started to do this on legitimate repos: