Gitpulse
Merged
Size
M
Change Breakdown
Refactor60%
Maintenance30%
Docs10%
#28111feat: Update naming of local gateway to computer use

Local gateway rebranded as computer use across n8n

DL
dlavrenuek
·Apr 7, 2026

The local AI gateway feature gets a consistent identity: n8n's local gateway package moves from @n8n/fs-proxy to @n8n/computer-use, with version 0.2.0 releasing session-bound permission confirmation.

The n8n local AI gateway feature had a naming problem. The package was called one thing (@n8n/fs-proxy), the umbrella feature another (Local Gateway), and the CLI commands yet another. Running npx @n8n/fs-proxy for "local gateway" functionality created friction for users trying to follow documentation or tutorials.

This rename brings everything under one roof: the package is now @n8n/computer-use, CLI commands read npx @n8n/computer-use, and system prompts reference "Computer Use" instead of "Local Gateway". Users connect their local machine to n8n by running one consistent command—no more hunting through docs to figure out which package name applies.

The version bump to 0.2.0 also releases instance-side permission confirmation, implemented in a companion PR. Permissions for AI agent operations on the local machine now bind to individual sessions rather than being global. This is part of a larger effort to make permission modes session-aware.

The rename touches the @n8n/computer-use package, @n8n/local-gateway desktop app, and @n8n/instance-ai backend across 62 files—but the underlying protocol and behavior remain unchanged.

View Original GitHub Description

Summary

Changes the naming of "fs-proxy" and "Local Gateway" to consistent "Computer Use"/"computer-use" (as package name). Bumps the version of computer-use to 0.2.0 to release instance-side permission confirmation implemented in https://github.com/n8n-io/n8n/pull/27910

Related Linear tickets, Github issues, and Community forum posts

https://linear.app/n8n/issue/NODE-4797/change-permission-modes-to-be-bound-to-session-and-not-globally

Review / Merge checklist

  • PR title and summary are descriptive. (conventions) <!-- **Remember, the title automatically goes into the changelog. Use `(no-changelog)` otherwise.** -->
  • Docs updated or follow-up ticket created.
  • Tests included. <!-- A bug is not considered fixed, unless a test is added to prevent it from happening again. A feature is not complete without tests. -->
  • PR Labeled with Backport to Beta, Backport to Stable, or Backport to v1 (if the PR is an urgent fix that needs to be backported)
© 2026 · via Gitpulse