Current Behavior
NX The Nx Daemon for 'd:\path....' received a message from a different workspace ('D:\path...') and refused to process it. This usually means multiple workspaces are sharing a socket directory; ensure NX_SOCKET_DIR (or NX_DAEMON_SOCKET_DIR) is not set to a shared location.
This happens when an AI in this case claude executes some nx commands ( like linting ), and you yourself with a powershell window try to run the same command yourself.
Currently to fix, is to stop claude, vscode, stop the deamon. And then try it yourself again. Digging through it it seems that claude in its shell lowercases the drive number while powershell passes it as uppercase.
Expected Behavior
Should work ( and did work before nx 23.2.0-beta.6
GitHub Repo
No response
Steps to Reproduce
Nx Report
NX Report complete - copy this into the issue template
Node : 24.18.0
OS : win32-x64
Native Target : x86_64-windows
pnpm : 11.9.0
daemon : Available
nx (global) : 23.0.1
nx : 23.2.0-beta.7
@nx/js : 23.2.0-beta.7
@nx/eslint : 23.2.0-beta.7
@nx/workspace : 23.2.0-beta.7
@nx/angular : 23.2.0-beta.7
@nx/cypress : 23.2.0-beta.7
@nx/devkit : 23.2.0-beta.7
@nx/eslint-plugin : 23.2.0-beta.7
@nx/node : 23.2.0-beta.7
@nx/oxlint : 23.2.0-beta.7
@nx/playwright : 23.2.0-beta.7
@nx/plugin : 23.2.0-beta.7
@nx/vite : 23.2.0-beta.7
@nx/vitest : 23.2.0-beta.7
@nx/web : 23.2.0-beta.7
typescript : 6.0.3
Nx key
---------------------------------------
(getPowerpackLicenseInformationAsync ?? getPowerpackLicenseInformation) is not a function
---------------------------------------
Community plugins:
@analogjs/vite-plugin-angular : 2.6.4
@analogjs/vitest-angular : 2.6.4
@jsverse/transloco : 8.4.0
@ngrx/component-store : 21.1.1
@ngrx/operators : 21.1.1
@ngrx/schematics : 21.1.1
@ngrx/signals : 21.1.1
@nx/azure-cache : 5.0.7
angular-eslint : 22.1.0
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
Current Behavior
NX The Nx Daemon for 'd:\path....' received a message from a different workspace ('D:\path...') and refused to process it. This usually means multiple workspaces are sharing a socket directory; ensure NX_SOCKET_DIR (or NX_DAEMON_SOCKET_DIR) is not set to a shared location.
This happens when an AI in this case claude executes some nx commands ( like linting ), and you yourself with a powershell window try to run the same command yourself.
Currently to fix, is to stop claude, vscode, stop the deamon. And then try it yourself again. Digging through it it seems that claude in its shell lowercases the drive number while powershell passes it as uppercase.
Expected Behavior
Should work ( and did work before nx 23.2.0-beta.6
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response