#19358·budibase

Show and confirm the exact action being escalated

Author: joebudiCreated Jul 28, 2026Updated Sep 14, 2026

Automatic per-tool escalation is implemented. Complete the security and UX around what reviewers are approving.

Reviewers should see:

  • The exact tool and action.
  • The resolved target, such as the table, row, API or recipient.
  • The important arguments and proposed changes.
  • Who requested it and which agent raised it.

The approved payload must be the same payload that executes. The agent must fail closed when no valid reviewer exists, and requesters should see whether the escalation is waiting, approved, rejected or expired.

Decide separately whether current-user confirmation is required. Generic tool risk labels are unnecessary unless they drive a real default behaviour.