What Orca leaves on your Mac.
Orca's workspaces are git worktrees. Devbroom assesses each one on its own with git itself, and shows the ones Orca already removed and half-finished setups separately.
Every folder has its own rule.
Devbroom handles every place the way Orca itself behaves. What the agent cleans itself it leaves to the agent; what has its own command it leaves to that command.
Workspaces
Git worktrees; each one is assessed on its own.
~/orca/workspacesRemoved workspaces
Workspaces Orca already removed, inside each repository.
<repo>/.orca-worktree-trashWorkspaces being set up
A setup that stopped halfway can leave files here; look inside.
~/orca/workspaces/.orca-preparingRecognizes Orca's worktrees by their traces.
It tells a worktree belongs to Orca from these traces; the stronger the trace, the more certain the ownership it shows.
- CertainAn
orca/folder in git metadata - LikelyA git admin name in Orca's
<number>-<uuid>form - LikelyInside the
~/orca/workspacesfolder
- Blocked if it holds unsaved work. git won't remove such a worktree without
--force; Devbroom never uses--force. - Blocked if a session runs in it or in its parent folder.
- Review if it has ignored files:
git worktree removedeletes them without asking.
Checks Orca's files first.
Before trusting an agent's data, Devbroom checks that its files are in the expected format. If they aren't, that data is only read; none of it counts as ready to clean.
A version outside this range still works if the format holds, and shows as “not tested yet”.
Only git worktrees are used, read with git itself; nothing relies on a file format of Orca's own.
Shows which version is installed on this Mac and whether it has been tested.