Approvals

Agents in Aplite do not quietly rewrite your workspace. When an agent wants to change a document — or take an action with effects outside the workspace — it proposes the change instead of making it. The proposal lands in Approvals, and nothing happens until you act on it.

What a proposal holds

A file edit arrives as a diff against the current version, so you see exactly what would change. You can approve it as-is, edit the proposed content first and apply your version, or reject it. On approve, the change is applied and the agent wakes to carry on from there; on reject, it learns the answer was no.

Where it lives

Approvals sit in the header of every screen, with a counter showing what is waiting — review from wherever you are. The queue survives you being away: nothing expires, nothing auto-applies.

Why it works this way

A routine that runs unattended should not require faith. Because every outward change queues here, an agent can work overnight and you read what it wanted to do in the morning. Routines like Inbox triage are built on this: the agent drafts the replies, and every draft is yours to send or bin.