[Bug] FSWatcher initialization fails with "Unknown Error, TODO"

Resolved 💬 3 comments Opened Dec 23, 2025 by GoosLab Closed Dec 27, 2025

Bug Description
This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason:
Error: Unknown Error, TODO
at watch (unknown)
at new FSWatcher (node:fs:29:31)
at watch (node:fs:296:23)
at AC_ (/$bunfs/root/claude:392:6265)

Environment Info

  • Platform: darwin
  • Terminal: vscode
  • Version: 2.0.76
  • Feedback ID:

Errors

[{"error":"Error: NON-FATAL: Lock acquisition failed for /Users/goos/.local/share/claude/versions/2.0.76 (expected in multi-process scenarios)\n    at XZR (/$bunfs/root/claude:2430:2165)\n    at fUA (/$bunfs/root/claude:2430:1885)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-23T12:39:09.506Z"},{"error":"Error\n    at ak (/$bunfs/root/claude:59:1144)\n    at <anonymous> (/$bunfs/root/claude:60:10093)\n    at emit (node:events:92:22)\n    at endReadableNT (internal:streams/readable:861:50)\n    at processTicksAndRejections (native:7:39)\n    at request (/$bunfs/root/claude:62:2149)\n    at processTicksAndRejections (native:7:39)","timestamp":"2025-12-23T16:01:22.901Z"}]

View original on GitHub ↗

This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗