Approve tool use in unattended runs
An approval prompt needs a person. Decide in advance whether Chetty may proceed when nobody is there to answer.
What an unattended run is
Interactive chat shows approval prompts in the web app and in the CLI. There is nobody to answer one in:
- a scheduled job;
- a platform channel conversation;
- a sub-agent working on its own.
In those runs an Ask rule either proceeds or is blocked, depending on one setting. A Deny rule still refuses the call, and read-only delegated work refuses Ask calls whatever the setting says.
Allow or block the question
Open Account → Models → Unattended runs and choose:
| Setting | What an Ask rule does |
|---|---|
| Allow | Proceeds without a prompt. This is the default. |
| Block | Refuses the call. |
Block is the safer choice for a scheduled job that must never improvise, and Allow suits a job you already trust. Existing rules are not changed by this setting; it only decides what happens to a question.
Choose YOLO mode
YOLO mode approves tool requests in new sessions without asking. The toggle in Account → Models sets the default for new sessions.
In elowen chat, /yolo toggles the current session, while /yolo on and /yolo off set it directly. A YOLO change in the CLI affects only that conversation.
Warning: YOLO never overrides a Deny rule and never overrides Block for unattended runs. Those two remain the guardrails to keep in place.
Check that it worked
Run the thing you configured and watch the outcome rather than assuming it:
- For a scheduled job, use Run now and open its History to see whether the run completed or was refused.
- For a channel conversation, read the reply in that conversation.
- For a delegation, read the child's result in the conversation that started it.
If a run refused a call, its history or transcript names the refusal. Then relax that one rule rather than switching everything to Allow.