Unable to re-enable Execute Command node in n8n 2.0

[etim808]

Bug Description

After upgrading to n8n 2.0, the Execute Command node is disabled by default as per the breaking changes documentation.
I've attempted to re-enable the node using the N8N_NODES_INCLUDE environment variable as suggested, but the node still does not appear in the node selector.
Environment:

n8n version: 2.0
Installation method: System install (npm global) with systemd service
OS: Linux (Debian-based)

Steps to reproduce:

Fresh n8n 2.0 install or upgrade from 1.x
Add N8N_NODES_INCLUDE=n8n-nodes-base.executeCommand to environment file (/opt/n8n.env)
Restart n8n via sudo systemctl restart n8n
Search for "Execute Command" in node panel — node does not appear

To Reproduce

Fresh n8n 2.0 install or upgrade from 1.x
Add N8N_NODES_INCLUDE=n8n-nodes-base.executeCommand to environment file (/opt/n8n.env)
Restart n8n via sudo systemctl restart n8n
Search for "Execute Command" in node panel — node does not appear

Expected behavior

Execute Command node should appear in the node selector after setting the environment variable and restarting.

Debug Info

null

Operating System

Debian LXC

n8n Version

null

Node.js Version

null

Database

SQLite (default)

Execution mode

main (default)

Hosting

n8n cloud

[n8n-assistant]

Hey @etim808,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-5979".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-5979

[MookieLian]

Thanks for bringing this up! After reviewing the details, it seems like the behaviour you've reported is actually expected and not a bug. We can understand how this might seem confusing, so we've added a note to clarify things.

If you have any questions or need more details, feel free to reach out again, we're here to help!

Note that the exact environment variable required is as follows: NODES_EXCLUDE="[]". After adding this variable, you should be able to see the nodes that were disabled by default in the nodes panel.

We will close this issue to keep our tracker focused on bug reports for now, but feel free to open a new issue if you are still encountering this.

Thanks again for being part of the n8n community!

#closed:working-as-expected