Approvals, input & authentication

Aghata pauses instead of guessing. There are exactly three pause states, and telling them apart makes every stuck task a thirty-second fix.

Approval — “may I do this?”

Triggered by risky or irreversible actions: sending an email, submitting an order, posting, paying, deleting. The approval card states the exact action and its target — “Send discrepancy report to finance@company.com” — and the task does nothing until you decide.

• Approve → the action runs, attributed to your approval in the session.
• Reject → Aghata re-plans around it or asks what you’d prefer.

Caution

There is no setting that silently disables approvals for irreversible actions. Paid plans buy more work, not fewer controls.

Input — “I need to know something.”

Triggered when your intent is ambiguous or a fact is missing: a budget, a preference, a choice between two defensible options. The card asks a specific question; your answer becomes part of the session record (and often a proposed memory, so you’re never asked twice).

Authentication — “this site needs a human.”

Browser-mode only. A captcha, a 2FA prompt, or a login you haven’t vaulted puts the session in paused for authentication. You log in through the live view — your keystrokes go to the website, never to the agent — and work resumes. See Browser mode for the vault details.

How you find out

Pauses surface in the task list, in the session itself, and in notifications. Paused tasks wait indefinitely; nothing expires into a silent failure while you’re at lunch.

For teams

On team plans, approvals can be escalated to whoever owns the call — a budget approval to the budget owner — and mentions pull a specific teammate into a session. Every approval records who made it.