My usage environment is Windows + VSCode. This is my.claude.json configuration.

**After I opened VSCode and then opened the project code in the mapped network drive, when I used the terminal in VSCode to start Claude with ccr code (Claude Code Router), the following error messages were displayed.**
:internal/fs/watchers:214
const error = new UVException({
^
Error: EISDIR: illegal operation on a directory, watch
at FSWatcher._handle.onchange (node:internal/fs/watchers:214:21)
Emitted 'error' event on rr1 instance at:
at rr1._handleError (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude
-code/cli.js:741:25507)
at _boundHandleError (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claud
e-code/cli.js:741:14101)
at file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:741:1
2839
at lr1 (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:
741:12294)
at $D1 (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:
741:12824)
at FSWatcher. (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/c
laude-code/cli.js:741:13269)
at FSWatcher.emit (node:events:518:28)
at FSWatcher.emit (node:domain:489:12)
at FSWatcher._handle.onchange (node:internal/fs/watchers:220:12) {
errno: -4068,
syscall: 'watch',
code: 'EISDIR',
filename: null
}
Node.js v22.18.0
After switching to another project code in the network drive and performing the corresponding operations, it can successfully connect to MCP. I don't know what the reason is.
My usage environment is Windows + VSCode. This is my.claude.json configuration.
Error: EISDIR: illegal operation on a directory, watch
at FSWatcher._handle.onchange (node:internal/fs/watchers:214:21)
Emitted 'error' event on rr1 instance at:
at rr1._handleError (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude
-code/cli.js:741:25507)
at _boundHandleError (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claud
e-code/cli.js:741:14101)
at file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:741:1
2839
at lr1 (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:
741:12294)
at $D1 (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:
741:12824)
at FSWatcher. (file:///C:/Users/102974%7E1.WIN/AppData/Roaming/npm/node_modules/@anthropic-ai/c
laude-code/cli.js:741:13269)
at FSWatcher.emit (node:events:518:28)
at FSWatcher.emit (node:domain:489:12)
at FSWatcher._handle.onchange (node:internal/fs/watchers:220:12) {
errno: -4068,
syscall: 'watch',
code: 'EISDIR',
filename: null
}
Node.js v22.18.0
After switching to another project code in the network drive and performing the corresponding operations, it can successfully connect to MCP. I don't know what the reason is.