claude-code - 💡(How to fix) Fix [Bug] Extra Usage toggle prevents API access after re-enabling with new tokens [1 comments, 2 participants]

[{"error":"Error: EPERM: operation not permitted, symlink 'C:\Users\MazdaCX5\.claude\projects\C--Users-MazdaCX5-Desktop-Hompage-Homepage\1c4128d9-c436-46e1-8b0d-b9987100b522\subagents\agent-a3c4152.jsonl' -> 'C:\Users\MazdaCX5\AppData\Local\Temp\claude\C--Users-MazdaCX5-Desktop-Hompage-Homepage\tasks\a3c4152.output'\n at symlinkSync (node:fs:1879:11)\n at ZWA (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1671:9904)\n at V92 (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1773:1191)\n at file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3172:21896\n at AsyncLocalStorage.run (node:internal/async_local_storage/async_context_frame:63:14)\n at CtA (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:237:14274)\n at Object.call (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3172:21619)\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)","timestamp":"2026-04-08T12:47:02.258Z"},{"error":"Error: EPERM: operation not permitted, symlink 'C:\Users\MazdaCX5\.claude\projects\C--Users-MazdaCX5-Desktop-Hompage-Homepage\1c4128d9-c436-46e1-8b0d-b9987100b522\subagents\agent-aa3a56b.jsonl' -> 'C:\Users\MazdaCX5\AppData\Local\Temp\claude\C--Users-MazdaCX5-Desktop-Hompage-Homepage\tasks\aa3a56b.output'\n at symlinkSync (node:fs:1879:11)\n at ZWA (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1671:9904)\n at V92 (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1773:1191)\n at file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3172:21896\n at AsyncLocalStorage.run (node:internal/async_local_storage/async_context_frame:63:14)\n at CtA (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:237:14274)\n at Object.call (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3172:21619)\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)","timestamp":"2026-04-08T12:47:02.542Z"},{"error":"Error: EPERM: operation not permitted, symlink 'C:\Users\MazdaCX5\.claude\projects\C--Users-MazdaCX5-Desktop-Hompage-Homepage\1c4128d9-c436-46e1-8b0d-b9987100b522\subagents\agent-a444e20.jsonl' -> 'C:\Users\MazdaCX5\AppData\Local\Temp\claude\C--Users-MazdaCX5-Desktop-Hompage-Homepage\tasks\a444e20.output'\n at symlinkSync (node:fs:1879:11)\n at ZWA (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1671:9904)\n at V92 (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1773:1191)\n at file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3172:21896\n at AsyncLocalStorage.run (node:internal/async_local_storage/async_context_frame:63:14)\n at CtA (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:237:14274)\n at Object.call (file:///C:/Users/MazdaCX5/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:3172:21619)\n at process.processTicksAndRejections (node:internal/process/task_queues:103:5)","timestamp":"2026-04-08T12:47:02.570Z"}]

TL;DR

The issue is likely due to a permission error when creating symlinks, and restarting the application or checking file system permissions may help resolve the issue.

Guidance

• The error messages indicate an EPERM: operation not permitted error when trying to create symlinks, suggesting a file system permission issue.
• Check the file system permissions for the directories involved in the error messages, such as C:\\Users\\MazdaCX5\\.claude\\projects and C:\\Users\\MazdaCX5\\AppData\\Local\\Temp\\claude.
• Try restarting the application or the system to see if the issue persists.
• Consider running the application with elevated privileges to see if the issue is related to permission restrictions.

Example

No code snippet is provided as the issue seems to be related to file system permissions rather than code.

Notes

The issue may be specific to the Windows environment, and the solution may involve adjusting file system permissions or configuring the application to use a different directory.

Recommendation

Apply workaround: Try running the application with elevated privileges or adjusting file system permissions to resolve the issue. This is recommended as the error messages suggest a permission-related issue, and adjusting permissions or running with elevated privileges may help resolve the issue.