n8n Feature Proposal: Option to Fully Disable Code Nodes and Eliminate Task Runners

Currently n8n unconditionally enables task runners, which are needed to execute Code nodes. The proposal advocates a supported configuration to opt out entirely-disallowing Code nodes and eliminating the need to start task runners. For regulated or high-security deployments (finance, healthcare, government), this capability is meaningful: it prevents arbitrary code execution, simplifies hardening, and reduces maintenance.

For enterprise buyers and platform operators, the absence of an opt-out is a blocker when strict change controls or compliance frameworks mandate no user-supplied code in automation platforms. Allowing a disable switch would enable n8n to be considered for a broader set of use cases and help centralize automation on platforms that can enforce safe, declarative actions via vetted nodes.

Implementation considerations for vendors and operators include: providing migration tooling to convert Code-node logic into reusable, approved nodes; exposing RBAC and policy-as-code to prevent re-enablement; ensuring the node catalog covers common extensibility needs; and documenting the security guarantees and trade-offs. From an operational standpoint, it's also beneficial to offer a hardened mode that disables task-runner binaries, reduces attack surface, and provides a clear compliance claim.

Actionable steps for business leaders evaluating n8n or similar platforms: request roadmap commitments for code-disabling features, insist on demonstrable policy controls and vetted node libraries, and plan migration strategies (replace custom scripts with managed nodes or external microservices). For vendors, prioritize a supported disable path alongside education on safe extension patterns-this widens addressable markets and reduces enterprise friction.