Unhandled ENXIO error when watching CDP socket pollutes logs

Description

When running Claude Code, unhandled promise rejections appear in the output related to watching temporary CDP socket files. These errors don't block functionality but pollute the logging output.

Error

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: ENXIO: no such device or address, watch '/tmp/node-cdp.4602-eb06ee52-77.sock'
    at watch (unknown)
    at new FSWatcher (node:fs:30:31)
    at watch (node:fs:300:23)
    at hLI (/$bunfs/root/claude:366:80958)
    at w60 (/$bunfs/root/claude:366:86171)
    at _watchWithNodeFs (/$bunfs/root/claude:366:81439)
    at _handleFile (/$bunfs/root/claude:366:82182)
    at _addToNodeFs (/$bunfs/root/claude:366:85209)
    at processTicksAndRejections (native:7:39)

Expected behavior

These transient socket watcher errors should be caught and handled silently, or logged at a debug level rather than appearing as unhandled rejections.

Environment

• Platform: Linux (6.14.0-119037-tuxedo)
• Running in: VS Code extension