HelpMessaging

Approvals and confirmations

Your assistants are designed to act. How much each one does on its own is set by you, per assistant.

The four levels

  • Works on its own: the default on a new install. It runs unattended, and a payment, a deploy or an outgoing email still waits for your yes.
  • Asks when unsure: commands it knows run. A new command goes to a reviewer model first, and reaches you only when the reviewer will not clear it. That is a review by a model rather than by you, which is why we do not call it an approval.
  • Asks first: commands it knows run. Every new command waits for you in the conversation. This is the level where a person decides.
  • Reads only: it can look, and cannot change anything.

What an approval looks like

When an assistant needs your go-ahead to run a command, a card appears in the conversation. Its title says which assistant is asking, for example Max wants to run a command, and under it Maxiful says in plain words what the command does. Show the command shows the exact command and the folder it runs in.

How to respond

  • Allow once: the command runs this time
  • Always allow here: the same command runs again in that folder without asking
  • Deny: the command is not run

A payment, a deploy or an email to a customer offers only Allow once and Deny. A waiting request also shows as a notice at the foot of the list on the left: choose it to open Approvals, where you can answer too. If nobody answers, the request expires, and a command that was never answered is not run.

Changing the level

In the Maxiful app, open Team, then Assistants, choose the assistant, and under How Max works (with your assistant's name in place of Max) choose Change. If the change needs the assistant to restart before it takes effect, Maxiful says so.

If nothing can reach you

Asks first fails closed. If nothing is connected that can ask you, the command is dropped rather than run.