AI Assistant now requires explicit admin opt-in
Admins must now explicitly enable n8n's AI Assistant through a modal that warns about risks before the feature activates. The choice is one-off — dismissed once, it won't reappear.
Before this change, the n8n AI Assistant feature could be enabled silently without users understanding what they were agreeing to. Now, admins are shown a welcome modal the first time they access the feature. The modal explains what the AI Assistant does — builds workflows through conversation, debugs failed executions, answers questions about n8n — and includes an explicit warning that the feature may behave unexpectedly and isn't recommended for production-critical workflows.
Admins choose to enable or disable the feature directly in the modal. Once dismissed, the modal won't appear again. The optional Computer Use gateway (for local file access and terminal commands) can be set up during this flow or skipped for later.
This opt-in requirement only applies to users with admin permissions. Standard users won't see the modal. The feature also includes renamed terminology throughout the UI: "n8n Agent" is now "AI Assistant."
The change touches the CLI settings service, frontend module system, and editor UI — ensuring the enabled state is tracked, synced between backend and frontend, and enforced at API endpoints.
View Original GitHub Description
Summary
Implements opt-in flow for users enrolled into the n8n Agent experiment :
- Forces choice of enabling or disabling feature
- Informs user of risks
- One-off : once dismissed, the user is not prompted for choice again
https://github.com/user-attachments/assets/ac49566d-2b6c-410d-9a85-79463c13ca54
<!-- Describe what the PR does and how to test. Photos and videos are recommended. -->Related Linear tickets, Github issues, and Community forum posts
<!-- Include links to **Linear ticket** or Github issue or Community forum post. Important in order to close *automatically* and provide context to reviewers. https://linear.app/n8n/issue/ --> <!-- Use "closes #<issue-number>", "fixes #<issue-number>", or "resolves #<issue-number>" to automatically close issues when the PR is merged. -->Review / Merge checklist
- I have seen this code, I have run this code, and I take responsibility for this code.
- 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)