AI consent flow simplified to three options

When AI agents request access to tools or resources, users previously faced five choices including permanent "Always allow" and "Always deny" options. Those persistent decisions have been removed from the instance UI, leaving just three session-scoped choices.
When AI agents need to access tools or resources, users see a consent prompt. Previously, the n8n instance UI offered five choices including permanent "Always allow" and "Always deny" options that would remember decisions across sessions.
The new flow presents just three options: "Deny once," "Allow once," and "Allow for session." The default action is now "Allow" instead of "Allow for session," reducing the chance of accidentally granting prolonged access. "Allow for session" remains available but moved to a dropdown.
The CLI tool continues to show all five options since it's a direct human interface where users can intentionally make persistent choices. The distinction is intentional — instance UIs see the simplified flow while CLI retains the full set.
This change targets decision fatigue in AI agent workflows, particularly when agents repeatedly request access to the same resources. By removing permanent decisions from the UI, users aren't burdened with remembering which resources they previously allowed or denied forever.
View Original GitHub Description
Summary
Simplifies the decisions in HITL for Computer Use.
- Removes
Always allowandAlways denyoptions which store the decision permanently between sessions for given resource. - Default "allow" choice is changed from
Allow for sessiontoAllow(once),Allow for sessionwas moved to the dropdown
Related Linear tickets, Github issues, and Community forum posts
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)