Pending Actions

When the agent wants to make changes, it creates a pending action that requires your approval. This ensures the agent never takes destructive or unintended actions without human oversight.

How It Works

You ask the agent to do something (e.g., “tag all pending orders as priority”)
The agent creates a pending action with details about what it will do
You review the action — including the scope and affected items
You approve or reject the action
If approved, the action executes

Pending Action Details

Each pending action includes:

Field	Description
`scope`	What will be affected (e.g., “42 orders”)
`action`	What will happen (e.g., “add tag: priority”)
`affectedItemCount`	Number of records that will change
`idempotencyKey`	Ensures the action can only execute once
`expiresAt`	Actions expire if not approved within a time window

Approving Actions

Portal

Click Approve or Reject on the pending action card in the chat.

API


POST /api/agent/actions/:id/approve


POST /api/agent/actions/:id/reject

Safety Guarantees

Actions with side effects always require approval
Read-only queries execute immediately (no approval needed)
Each action has an idempotency key — approving twice won’t double-execute
Actions expire after a configurable time window
The agent shows exactly what will happen before you approve