Approvals
Understand when work runs automatically, when it waits, and what approval authorizes.
An approval lets you inspect an action before Botchi performs it. Permission to use a tool and permission to run this particular action are separate checks.
Dashboard changes
The dashboard Assistant reads account state automatically. Ordinary configuration changes and external writes wait for a proposal you approve or deny. Viewers receive a read-only Assistant.
A proposal describes the actual change, including its target and values. Related proposals from the same assistant step can be reviewed together. Only selected changes are confirmed; a confirmation is followed by execution and a result.
Eval case maintenance and suite execution are exceptions: they run without confirmation. Evals simulate writes, but suite runs still consume Sparks.
Agent tool policies
Each assigned tool has its own policy on each agent. Auto executes without stopping, Ask waits for approval, and Off blocks execution. A recommended policy is a starting suggestion, not an account-wide rule.
Runs automatically, without stopping
Pauses and waits for a person
Never runs, in any context
Every externally connected MCP tool starts at Ask, regardless of the server's claimed risk. Change that policy only when you trust the tool unattended.
Plans and unattended workflows
Read-only plans run automatically. A plan containing gated steps waits for one approval covering the whole displayed plan. Approve plan authorizes that plan; Deny runs none of it. Plans cannot be edited or set to always approve.
Watch out — Workflows cannot wait for a person. Their agent steps execute Ask tools automatically; Off tools stay blocked. Grant only capabilities you trust unattended.
Your automations and background tasks
Your scheduled automations and Botchi's background tasks run without you, so nothing can wait for an approval. When you create or change one in chat, Botchi shows what it will do on its own, such as sending an email: approving allows those actions for that automation only. You can review them in the automation's form.
Actions set to Always ask or Block in your tool settings never run in the background. When a run needs an action you have not allowed, it does the rest and tells you in chat what it could not do. Changing an automation's instructions removes its approved actions until you approve them again.
Stopping a response does not undo completed actions. Review the recorded result before repeating work, especially when an external service may already have applied a change.