Approvals
What Aldwin asks before it acts, and how to allow or deny it in the browser.
Aldwin asks before it does anything that changes something: running a command, editing or creating a file, downloading, changing a memory note or its persona, saving a skill, or making a change in a connected app. Reading, searching, and looking things up do not ask.
What you see#
When Aldwin needs your OK, it pauses and shows a card in the chat, at the step it wants to take. The card shows exactly what will happen:
- A command: the full command it wants to run.
- A file edit: the change, with removed lines in red and added lines in green.
- An app action: what it will do, and in which app.
While a card waits, the message box is locked. If you scrolled away, the Aldwin needs your OK button takes you back to the card.
Your answer#
| Button | What happens |
|---|---|
| Allow | Aldwin takes this one step |
| Always allow in this chat | Aldwin takes this step, and won't ask again for the same file, folder, or app action in this conversation. The card says what it covers. Only offered for some steps |
| Deny | Aldwin does not take the step. You can add a reason, up to 280 characters, so it can try another way |
Nothing happens until you select a button. Pressing Esc does not answer the card. To end the whole answer instead, select Stop.
After you answer, the card stays in the chat marked Approved or Denied, so you can see later what you agreed to.
Good habits#
- Read the command or the change before you allow it.
- Deny anything you do not understand, and say why in the reason box.
- Use Always allow in this chat only for steps you are happy to repeat.
If the connection drops#
A card that is waiting survives a short drop in the connection. Once the page reconnects, you can still answer it. Reloading the page loses the card. If Aldwin gets no answer in time, it treats the step as denied.
More on how Aldwin keeps you in control: Safety.