Skip to content

Retire Dev Artifacts tree rescan - #71

Open
huntharo wants to merge 6 commits into
mainfrom
codex/dev-artifact-rescan-speed-cancel
Open

huntharo wants to merge 6 commits into
mainfrom
codex/dev-artifact-rescan-speed-cancel

Conversation

@huntharo

@huntharo huntharo commented Sep 28, 2026 •

Copy link
Copy Markdown
Owner

Summary

I retired Dev Artifacts' separate "Rescan trees" action. It walked up to 2,500 saved roots using Node.js file stats, could take longer than the optimized drive scan, and showed a progress total that differed from the listed-tree count. The header's Rescan is now the only way to refresh the drive's Dev Artifacts. It uses the normal scanner, can be stopped from the header, and supplies a new Dev sidecar when it finishes.

I removed the unused tree-rescan IPC, worker path, progress UI, and tests. The folder-tree classification fallback for older scans remains available.

Verification

  • I verified the header Rescan refreshes Dev Artifacts in the built app, with no second rescan action in the tab. All 3 Dev Artifacts E2E tests pass.
  • Typecheck and 52 focused unit, scaling, worker, and renderer I/O-budget tests pass.
  • The full unit suite has 797 passing and 13 failing tests on this macOS host. Failures are in unrelated I/O-budget scenarios, mostly child-process settle timeouts (diskutil, tmutil, osascript); one Folders LRU budget also differs from its recorded counts.

@huntharo huntharo changed the title Use drive scanner for Dev Artifacts refresh Retire Dev Artifacts tree rescan Sep 28, 2026
huntharo pushed a commit that referenced this pull request Oct 14, 2026
Let AI agents drive DiskHound over a local MCP server
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant