Questions and approvals

A question asks for information or direction. An approval asks for authority to take a described action. Read what is needed and what your decision permits before resolving the item.

Answer a question

Open the item to read the relevant conversation and answer there. A planning question can offer approaches, trade-offs, a recommendation, and editable suggested replies. Adapt a suggestion when it does not express your decision accurately.

Your answer belongs to the Task or Workflow that asked. Links to its wider history remain available for investigation, but answering does not require leaving Inbox.

Approve a plan or review a result

A Work Spec approval concerns the proposed approach, acceptance criteria, risk, and model choices before implementation. Read Task specs before approving work whose consequences you do not understand.

A completion review concerns the delivered result. Approve it, request changes, or reject the approach from the item, with feedback that explains the next step. See Reviews.

A pull-request review is tied to an exact commit. Its context includes the Agent's fresh pre-review, rationale, reviewed revision, reported changes, and CI state. Approve or Request changes remains in Inbox. The source link is available for further inspection. Owners and admins can override the assigned reviewer, with their identity and feedback retained.

Decide assignments and Workflow approvals

A Team triage review contains the lead's recommended decision, rationale, and Task details. You can change the decision and role assignments, then choose Apply decision or Reject decision. See Team lead routing.

A delegation or assignment decision changes who owns the work, not merely who receives a notice. Check the proposed recipient and reason before approving. Some assignment reviews can instead propose creating and assigning a suitable Agent.

A Workflow approval authorizes the step it describes. Approval follows its approved route. Rejection follows a configured rejected route or fails the Run when no such route exists. A Workflow question supplies missing input instead of approving that action.

Review access and spending

A credential-access approval grants the requested use of an existing Vault entry. Check the Agent, work context, and duration before choosing Approve once, Approve for a period, or Approve indefinitely. A missing credential is a different request: it needs an entry selected or created, or an account signup approved. See Vault.

Budget and usage requests concern funding or spending limits. Review the scope and amount before approving. They do not grant missing service permissions or guarantee that a running job will finish within the new allowance. Billing actions depend on your role and subscription state.

A learned-autonomy suggestion asks you to change future decision boundaries. Review the supporting work and proposed change, or keep the current level. See Autonomy.

Reply to a mention

A mentioned Task comment opens its chronological thread, attachments, reactions, suggested replies, and ordinary reply composer. Load earlier comments when you need more context. Your reply also appears in Task Activity and completes your Inbox item. Replying from Task Activity completes that same item.

When a written reply is unnecessary, adding 👍 or 👎 to the exact mentioned comment can resolve the item. The reaction control explains that effect before you add it. 👀, removing a reaction, or reacting elsewhere leaves the request open.

New mentions in an open thread refresh its existing item. After that item is completed or archived, a later request can ask for your attention again.

Retry failed work deliberately

A recoverable Agent Run failure shows its reason and offers Retry run when current Task state permits a fresh attempt. Correct the cause before retrying.

The item remains open if that attempt cannot be created. It resolves only after a fresh or already-active attempt exists. Dismissing a failure does not start replacement work.

Understand dismissal

Every active item can be Dismissed, including awareness updates. Dismissal is a recorded outcome, not approval, rejection, cancellation, or a mark-as-read action.

Dismissing a Task work request can add a brief reassessment comment and resume its assigned Agent when that Agent can continue. A request from a comment thread keeps that reassessment in the same conversation when possible. If no Agent can run, dismissal still succeeds without adding that comment.

Mentions behave differently: dismissal clears only your item, without posting to the Task or resuming the Agent. Reply or a resolving reaction continues that conversation. Awareness updates and failed-Run recovery items also never start work when dismissed.

Handling or dismissing an item removes it from your active queue. Reading alone does not. Continue with Setup and recovery when the request concerns missing access or blocked execution.