Skip to content

Clarify and align code diff permission semantics for Agent decides vs Always allow #9784

@peicodes

Description

@peicodes

Feedback from #feedback-app: users are confused by Always allow vs Agent decides for code diffs. Current behavior appears to treat Agent decides as always asking, which conflicts with docs language and user expectation.

Thread context indicates this mismatch has existed for a long time and creates enterprise-user confusion.

Slack source: https://warpdev.slack.com/archives/C08KTPNQN65/p1775745466445719

What needs to be done:

  • Clarify intended product behavior for code-diff permission modes (Always allow, Agent decides, Always ask).
  • Align implementation and documentation (or update labels/copy) so observed behavior matches what users are told.

Linear: APP-3944

Metadata

Metadata

Labels

area:agentAgent workflows, conversations, prompts, cloud mode, and AI-specific UI.area:code-reviewGit diff views, review UI, review comments, and PR-focused agent flows.area:settings-keybindingsSettings UI, preferences, keybindings, and keyboard-shortcut management.bugSomething isn't working.documentationImprovements or additions to documentation.repro:highThe report includes enough evidence that the issue appears highly reproducible.triagedIssue has received an initial automated triage pass.warp:prioritizedIssues prioritized by the Warp team.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions