Config mismatch: npm-global vs unknown runtime
Bug Description
Claude Code Status v1.0.55
L Session ID: d00b7990-84a5-4b9e-bcd2-c6ff27828293
Working Directory
L D:\ai_project\claude_test
System Diagnostics • /doctor
⚠ Config mismatch: running npm-global but config says unknown
IDE Integration • /config
L Installed PyCharm plugin but connection is not established.
Please restart your IDE or try installing from https://docs.anthropic.com/s/claude-code-jetbrains
Environment Info
- Platform: win32
- Terminal: pycharm
- Version: 1.0.55
- Feedback ID:
Errors
[{"error":"AxiosError: Request failed with status code 403\n at Tz (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:544:1070)\n at Unzip.KA (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:545:9946)\n at Unzip.emit (node:events:530:35)\n at Unzip.emit (node:domain:489:12)\n at endReadableNT (node:internal/streams/readable:1698:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n at ma.request (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:547:2081)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async $X6 (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:746:29763)\n at async I (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:640:31714)\n at async CV2 (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:746:30203)\n at async FAA.doExport (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:746:30877)","timestamp":"2025-07-18T09:47:42.711Z"},{"error":"AxiosError: Request failed with status code 403\n at Tz (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:544:1070)\n at Unzip.KA (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:545:9946)\n at Unzip.emit (node:events:530:35)\n at Unzip.emit (node:domain:489:12)\n at endReadableNT (node:internal/streams/readable:1698:12)\n at process.processTicksAndRejections (node:internal/process/task_queues:90:21)\n at ma.request (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:547:2081)\n at process.processTicksAndRejections (node:internal/process/task_queues:105:5)\n at async SB4 (file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1401:467)\n at async Promise.all (index 0)\n at async file:///C:/Users/ricosr/AppData/Roaming/npm/node_modules/@anthropic-ai/claude-code/cli.js:1387:6171","timestamp":"2025-07-18T09:49:29.892Z"}]
8 Comments
same as me
same as me
Same here! Now Claude Code 1.0.56. And, I presume this is related:
/migrate-installeralways fails.Same issue here (running
claude1.0.58onWindows 10 Pro N22H219045.6093usingnode24.3.0andnpm11.4.2).After running
claude config set --global installMethod npm-global, the config mismatch warning message that shows up when you run/statusinclaudestill persists:<img width="667" height="53" alt="A cropped screenshot of the preceding error message" src="https://github.com/user-attachments/assets/93f4cab1-804d-416b-9575-36cd2c45b2de" />
Regardless, if
claudecan correctly determine at runtime that it is in fact running vianpm-global, what is the need for a second source of truth on the matter to even exist? (read:installMethod).Don't get me wrong, I'm all for controlling runtime behaviour through configuration.
But
installMethodapparently does not preventclaudefrom being installed, nor from running, via any otherinstallMethod?This renders
installMethodneither prescriptive, nor even informative (as it can clearly differ from the actuality of the situation, as detected and reported byclaude?try
it works
It works for me too, thanks!
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.