Computer Use docs updated with new permission model
The n8n Computer Use README has been overhauled with clearer permission guidance, new filesystem write tools, and a three-tier deny/ask/allow model that replaces simple enable/disable toggles.
n8n's Computer Use documentation has been updated to reflect a new permission architecture and expanded capabilities. The README now describes a three-tier permission model — deny, ask, and allow — replacing the previous enable/disable flags for each capability. Shell execution and computer control default to deny, while filesystem reads default to allow and writes prompt for confirmation. Users can now manage these permissions via new CLI flags like --permission-shell and --permission-filesystem-read, or through corresponding environment variables.
The documentation also introduces filesystem write tools previously missing from the README: write_file, edit_file, create_directory, delete, move, and copy_file. The startup banner has been refreshed with new ASCII art reflecting the "Computer Use for n8n Assistant" branding. Browser automation defaults to Chrome instead of Chromium, and programmatic library configuration has been removed from the documentation — the README now focuses on CLI usage only.
The changes live in the @n8n/computer-use package, updating both the logger banner and the README that guides users through setup and permissions.
View Original GitHub DescriptionFact Check
Summary
Updates the Computer Use branding and readme that I forgot to do in https://github.com/n8n-io/n8n/pull/28111
Old startup banner <img width="668" height="130" alt="Bildschirmfoto 2026-04-09 um 12 04 30" src="https://github.com/user-attachments/assets/ffadac00-dde0-4106-8997-900c7dc08aff" />
New startup banner <img width="669" height="120" alt="Bildschirmfoto 2026-04-09 um 12 04 39" src="https://github.com/user-attachments/assets/8d5f8a23-b568-4bc4-977e-12d89501f9b7" />
Related Linear tickets, Github issues, and Community forum posts
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, orBackport to v1(if the PR is an urgent fix that needs to be backported)