# Reported issues for nx-console

Pod holds 18 of 29 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user.

Back to [nx-console](/mcp/nx-console).

## Most discussed

### NX Console 18.74.5 hangs forever in Cursor 2

<!-- Please do your best to fill out all of the sections below! -->

## Current Behavior

On Windows 11, I have upgraded to Cursor 2, and bumped NX Console to 18.74.5. I hangs forever and is not able to list projects. The same version of NX Console works as expected in VSCode 1.105.1. and Kiro 0.5.0.
I'm using NX 22.0.2. **Downgrading to Nx Console 18.74.4 works in Cursor**.

## Expected Behavior

I expect it to list projects and be able to run tasks from the NX Console gui

## Steps to Reproduc

[Read the thread](https://github.com/nrwl/nx-console/issues/2858) · 2025-10-31 · closed · external user · 31 comments

### 100% CPU Usage

<!-- Please do your best to fill out all of the sections below! -->

## Current Behavior

Enabling the Nx Console extension in a new Nx project constantly uses 100% CPU.

No projects load in the Nx Console panel.

## Expected Behavior

Not 100% CPU usage.  Projects load in Nx Console panel.

## Steps to Reproduce

<!-- ⚠️ IMPORTANT: A clear reproduction is essential for us to fix the issue! -->

<!-- Please provide one of the following (in order of preference): -->
1. Open VS Code or Cursor
2. H

[Read the thread](https://github.com/nrwl/nx-console/issues/2921) · 2025-12-12 · closed · external user · 12 comments

### NX MCP server not working in vscode copilot

<!-- Please do your best to fill out all of the sections below! -->

## Current Behavior

<!-- What is the behavior that currently you experience? -->
No usage of NX mcp server, it just runs terminal commands now

## Expected Behavior

<!-- What is the behavior that you expect to happen? -->
<!-- Is this a regression? .i.e Did this used to be the behavior at one point?  -->
it should use nx mcp server , even when told to,but  it never does so any more it just runs terminal nx commands. It used t

[Read the thread](https://github.com/nrwl/nx-console/issues/2710) · 2025-08-21 · closed · external user · 10 comments

### Nx Console fails to activate when the same Nx workspace is opened from a different directory path

## Current Behavior

Nx Console fails to activate when the same Nx workspace is opened from a different absolute directory path than the one it was originally initialized in.

Scenario:

- I have an Nx monorepo.
- The repository contents are periodically mirrored between directories using a PowerShell + robocopy `/MIR` workflow.
- At different times, I work on the exact same repository contents from different root paths (e.g., `R:\monorepo` and `C:\TEMP\monorepo`).

If Nx Console was first initi

[Read the thread](https://github.com/nrwl/nx-console/issues/3051) · 2026-02-16 · closed · external user · 7 comments

### Missing Option for NX Configure MCP Server in vscode

<!-- Please do your best to fill out all of the sections below! -->

## Current Behavior

After updated VsCode plugin to version later than 18.61.0, the option **Nx: Configure Nx MCP Server** is not available, like the screenshot below:

<img width="688" height="164" alt="Image" src="https://github.com/user-attachments/assets/d8ab0c15-37e9-43de-b8d1-c209c959c0fa" />

This situation has been confirmed across versions 18.61.0, 18.61.1, 18.62.0, 18.63.0

The Nx plugin in Vscode would pick a port wi

[Read the thread](https://github.com/nrwl/nx-console/issues/2695) · 2025-08-14 · closed · external user · 7 comments

### [Cursor 3.7.12] Nx Console fails to activate - TypeError: n.onDidReceiveFeedback is not a function

## Current Behavior

Nx Console fails during extension activation in **Cursor**, causing the Projects sidebar to hang indefinitely on **"Loading Nx workspace..."**.

On activation, the extension throws:

```
TypeError: n.onDidReceiveFeedback is not a function
```

Activation aborts before the Projects UI is wired up. The Nx Language Server and MCP server still start and successfully load the workspace, but the sidebar never receives workspace data.

This occurs on Nx Console **18.100.5** and **1

[Read the thread](https://github.com/nrwl/nx-console/issues/3156) · 2026-06-06 · closed · external user · 6 comments

### [Webstorm] various issues

## Current Behavior

I installed the mcp server in webstorm and:
1.  it launched 2 processes
2. with high memory usage
3. closing WebStorm did not terminate these processes.

I don't know how I can provide more data

##Expected Behavior

For the MCP server to run without issues.

## Steps to Reproduce

1. click on the "install mcp server" notification inside the ide

### Logs (Required)

I added `#dev.nx.console:trace` but I couldn't find any logs higher than INFO, anything about the mcp itself.

[Read the thread](https://github.com/nrwl/nx-console/issues/2916) · 2025-12-03 · open · external user · 6 comments

### Allow disabling minimal mode when running MCP via VS Code extension

<!-- Please do your best to fill out all of the sections below! -->
<!-- Use this issue type for concrete suggestions, otherwise, open a discussion type issue instead. -->

## Description

Per this code:

https://github.com/nrwl/nx-console/blob/132f80f2ec28531c01662c02e646bece9e975f82/libs/vscode/mcp/src/lib/init-mcp.ts#L243

It seems there is no way to use all the available tools when using the MCP server integration in VS Code.  
Is it possible to add an option to disable `minimal` mode?

## M

[Read the thread](https://github.com/nrwl/nx-console/issues/3150) · 2026-05-23 · open · external user · 5 comments

## Most recent

### Nested projects not shown in Projects tree view; visible in list view and PDV (regression)

## Current Behavior

In the Nx Console **PROJECTS** panel using the **tree** viewing style (`nxConsole.projectViewingStyle: "automatic"`, which resolves to tree), projects whose root directory is **nested under another project's root** are not displayed at all.

Our workspace has aggregator projects at `e2es/parent-*`, e.g. `e2es/parent-d` (root = `e2es/parent-d`) and many child projects nested beneath it, e.g. `e2es/parent-d/child-a-e2e`. The tree renders only the parent (`parent-d-e2e`) as a l

[Read the thread](https://github.com/nrwl/nx-console/issues/3193) · 2026-08-10 · open · external user · 0 comments

### [nx-mcp] nx_project_details fails with Nx 22.7+ because it bypasses the dist/src fallback

## Current Behavior

`nx_project_details` fails for every project when `nx-mcp@0.25.0` is used
with a published Nx version whose internal JavaScript files are located under
`nx/dist/src/**`.

This is reproducible with Nx 23.0.1 and the `node-modules` Yarn linker. It is
not a Yarn PnP issue.

Other tools such as `nx_workspace` work, and the equivalent resolved CLI
command also works:

```bash
yarn nx show project <existing-project-name> --json
```

The failure appears to be caused by `find-matchi

[Read the thread](https://github.com/nrwl/nx-console/issues/3186) · 2026-07-25 · closed · external user · 0 comments

### Supply Chain Attack on nrwl.angular-console - versions 18.94.0 and/or 18.95.0

**Summary**
On May 18, 2026, versions 18.94.0 and/or 18.95.0 of nrwl.angular-console (Nx Console) were auto-installed by VS Code on my machine and executed a malicious payload that:

1. Stole a GitHub OAuth token with workflow scope from VS Code's authentication store
2. Used that token to push a malicious GitHub Actions workflow to two branches of a private repository, designed to exfiltrate all repository secrets
3. Installed a persistent command-and-control (C2) backdoor on the machine as a m

[Read the thread](https://github.com/nrwl/nx-console/issues/3148) · 2026-05-20 · closed · external user · 2 comments

### SECURITY: v18.95.0 executes obfuscated payload from dangling commit on nrwl/nx via npx on workspace activation

## Summary

`nrwl.angular-console` **v18.95.0** on the VS Code Marketplace executes `npx -y github:nrwl/nx#558b09d7ad0d1660e2a0fb8a06da81a6f42e06d2` on workspace activation. The referenced commit is a **dangling commit on nrwl/nx whose tree has been replaced with a 2-file obfuscated dropper**. On my machine (2026-05-18, ~16:34 BST) this dropped a Python C2 backdoor + LaunchAgent. v18.94.0 is unaffected.

## Evidence

### 1. Injected code in v18.95.0 main.js

```
js
var U0 = require("vscode"),

[Read the thread](https://github.com/nrwl/nx-console/issues/3140) · 2026-05-18 · closed · external user · 1 comment

### Feature Request: Support nx_current_running_tasks_details / nx_current_running_task_output in standalone `npx nx mcp`

## Feature Request

### Current Behavior

The `nx_current_running_tasks_details` and `nx_current_running_task_output` MCP tools are only available when using Nx Console as the MCP host (e.g., via VSCode Copilot or Cursor). They are **not available** when using the standalone `npx nx mcp` server.

This means terminal-based AI tools (e.g., [OpenCode](https://github.com/nicepkg/opencode), Claude Code, or any MCP client connecting via stdio) cannot access running Nx TUI task logs — even when the TUI

[Read the thread](https://github.com/nrwl/nx-console/issues/3097) · 2026-03-17 · open · external user · 2 comments

### Nx MCP server in OpenAI Codex cause RAM usage spike

### Current Behavior

I have the Nx MCP configured to work with Codex in VS Code on Windows 11. Whenever I open the Codex extension, a Node Javascript runtime gets spun up and instantly starts consuming 16-20 GB of RAM and close to like 90% CPU usage. Unknown why, but sometimes the memory usage just keeps climbing as well. My computer locks up and I have to do a hard reset more often than not. 

### Expected Behavior

Using the Nx MCP server in VS Code does not cause a huge memory drain and Agen

[Read the thread](https://github.com/nrwl/nx-console/issues/3070) · 2026-01-24 · open · external user · 3 comments

### Nx Console fails to connect to self-hosted Nx Cloud server (using self-signed TLS cert)

## Current Behavior

Nx Console plugin for VS Code fails to connect to self-hosted Nx Cloud server (using self-signed TLS cert).

## Expected Behavior

Nx Console plugin for VS Code should be able to connect to self-hosted Nx Cloud server (using self-signed TLS cert).

It does not seem that `httpRequest` on https://github.com/nrwl/nx-console/blob/master/libs/shared/utils/src/lib/http-client.ts#L27C23-L27C34 respects `nxCloudProxyConfig` configured via `nx.json`.

## Steps to Reproduce

I suppose

[Read the thread](https://github.com/nrwl/nx-console/issues/2930) · 2025-12-29 · closed · external user · 3 comments

### nx pulling unqualified npm packages

## Current Behavior

When I run a first nx console command, or when I run `nx reset` and then an nx console command, a shell appears saying "npm install nx@latest" (this is a windows machine, so I can sometimes see sub-processes flashing up in a shell):

I reported this to @security@nrwl.io before (subject "nx pulling unqualified npm packages"), in their response Thursday, November 27 they asked me to open a ticket with you.

## Expected Behavior

Given the recent incident https://github.com/nr

[Read the thread](https://github.com/nrwl/nx-console/issues/2910) · 2025-12-01 · closed · external user · 3 comments

### nx-mcp (Streamable HTTP): server crashes on handshake with "Tool nx_docs is already registered" (double registration)

## Current Behavior

When running **nx-mcp** with the **Streamable HTTP** transport and connecting an MCP client, the server crashes during the initial handshake with:

```
Error: Tool nx_docs is already registered
    at .../node_modules/nx-mcp/main.js:...
Node.js v22.18.0
```

From the server logs you can also see **"Registering all Nx MCP tools"** printed once at startup and **again at the time of the first HTTP connection**, right before the crash. This indicates tools may be registered twic

[Read the thread](https://github.com/nrwl/nx-console/issues/2845) · 2025-10-25 · closed · external user · 2 comments

### nx-mcp (STDIO): `notifications/message` uses `{ level, message }`  but MCP 2025-06-18 requires `{ level, data, logger? }` → strict clients drop connection

## Current Behavior

When running **nx-mcp** over **STDIO**, the server emits logging notifications as:
```json
{ "jsonrpc": "2.0", "method": "notifications/message", "params": { "level": "info", "message": "..." } }
```
The current MCP spec (revision **2025-06-18**) defines the logging notification payload as:
`{ level, data, logger? }` — i.e., **`data`** instead of `message`.

Strict clients that implement the 2025‑06‑18 schema reject the legacy `{message}` payload, fail to parse the notificat

[Read the thread](https://github.com/nrwl/nx-console/issues/2844) · 2025-10-25 · closed · external user · 3 comments

The remaining reports are on [the project's issue tracker](https://github.com/nrwl/nx-console/issues).