Agents, tasks, and approvals

CORA delegates substantial work to specialist agents. Every durable unit of work becomes a task so it can be reviewed, queued, retried, observed, and audited.

Task lifecycle

• Proposed means a plan or exact action is waiting for a person.
• Approved means a person accepted the proposed payload.
• Queued means the worker is waiting to pick it up.
• Running means the executor or specialist is working.
• Completed means the action or deliverable finished.
• Rejected, cancelled, or failed explains why work did not complete.

Open More apps -> Inbox to see tasks by status. Tasks created from chat also appear as live cards inside the conversation.

Plan approval

For multi-step specialist work, CORA can draft a plan first, depending on the workspace's plan approval setting. Approve it to begin, reply in chat to revise it, or cancel it. Plans expire when they are left waiting so an old request does not run unexpectedly later.

Exact action approval

For state-changing operations, the approval should show the exact proposed payload. A settings change, for example, shows each field's value before and after. Approval is bound to those values; the executor cannot broaden the change after approval.

At execution, CORA re-checks permissions and the old value. If someone changed the setting after the preview was created, the task fails safely and asks for a fresh proposal.

Trust levels

Each action has a default approval rule. Workspace administrators can make an action stricter than its default, never looser, and an agent may ask for a stricter approval on a specific task but never a looser one.