Task approvals

An approval is a pause before an operation proceeds. Read what the action will change, which account or destination it targets, and why Nock is asking. A task can remain active while waiting for this decision.

Review one action

The approval queue lists pending operations with Accept and Reject controls. Selecting the explanatory text can provide more detail. With multiple operations, Accept all and Reject all apply to the queue; use an individual row when you want to authorize only one.

For a connected-app action that exposes editable fields, check the recipient, subject, body, or other destination information. Edit the fields before confirming. The app can show Applying your edits… while the agent prepares the revised action, followed by its execution state. Wait for the result and check the destination service for consequential changes.

The presence of an approval UI does not mean a service is connected or available. A request can still fail after approval because of authentication, account access, provider restrictions, or an unavailable integration.

Answer by voice

While a request is pending, a plain “yes” or “no” can answer it. Without an “all” qualifier, the response applies to the oldest pending action. When several unrelated tasks are waiting, using the visible row is the clearest way to choose the intended one.

“No, send it somewhere else” is a new instruction rather than a simple confirmation. If you want to change the task, decline the original operation and state the new target clearly. General praise is not reliable authorization; use the explicit controls for actions that matter.

Decline, stop, or let it expire

Declining refuses the operation and ends the associated request rather than inviting the agent to find another way around the decision. Stopping a request also cancels its pending actions. It cannot undo operations that already completed externally.

Ordinary agent approval cards expire after ten minutes. An expired card displays Expired — declined for you and can no longer be accepted. Ask again if you still want the operation, after checking whether any earlier step already changed something.

Coding integrations have their own question and permission lifecycle. Do not apply the ordinary card’s ten-minute rule to every coding prompt; see Coding task troubleshooting.

Settings and widget actions

Some changes use a native operating-system confirmation dialog, including selected permission changes and installing a local program as an integration. Read that dialog even if an earlier conversational card was already approved.

Widget buttons that perform actions can also require confirmation. Review them as operations, not decorative interface controls. Changing access preferences does not make every operation available, and a named agent’s instructions do not override account or tool restrictions. See Permissions and Widget builder.