Human in the loop

The assistant does not guess on things that matter, and it does not act on sensitive requests without checking with you first. Both show up as a card in the chat.

​

When the assistant asks a question

The assistant asks when it needs information only you can give, or when a step is genuinely ambiguous, such as which of two matching accounts you meant. A question can arrive as option cards you tap to answer, free text you type yourself, or both together. Answer directly in the chat. There is nothing else to configure.

Which of these two events did you mean: “Design Meetup” on the 12th, or “Design Meetup Berlin” on the 19th?

The assistant does not ask for confirmation on everything, only where the answer actually changes what it does next.

​

What needs your explicit approval

Some actions are sensitive enough that the assistant always stops and shows you an approval card before doing them, no matter how the request was phrased:

• Creating a subscription Cloud Phone
• Resetting a device to a clean state
• Permanently removing a temporary, pay-as-you-go phone
• Cancelling a managed proxy or deleting one you brought yourself
• Deleting a recording

Creating a pay-as-you-go phone is different: the assistant asks you to confirm per-minute billing in the conversation itself, and only creates the phone after you clearly agree. You can approve or decline. Approval applies only to that one request; the next reset, shutdown, or deletion asks again. Declining stops the action; nothing happens. Everyday, reversible steps, like installing an app or filling out a form, do not need this card. It is reserved for actions you cannot casually undo.

​

Saving a login

If a task needs you to log into an app for the first time, the assistant does not ask you to type your password into the chat. It shows a secure card where you enter your credentials directly. Afterward the assistant only knows a reference to them, never the actual value.

Save my login for this app so future runs don’t need to ask me again.

If a session on the device is already active, the assistant skips the login step entirely rather than asking you to save anything.

​

If you do not answer

A question waits for you, and the job is not marked as failed while it is paused. An approval card expires after about ten minutes; if you come back later, send a new message and the assistant asks again. If a conversation sits unanswered long enough to go stale, the assistant reports the job as incomplete along with what it was waiting on.

​

Leaving the tab and coming back

If the job is running on a phone, closing the chat does not stop it. Work already in progress on the device continues. When you reopen the conversation, it catches you up automatically, including any question or approval that is still waiting for you. You do not need to scroll back through everything that happened while you were away. If you would rather not check back manually, set up notifications so you hear the moment the assistant finishes, fails, or needs your answer. See Notifications.

​

Stopping a running job

Ask the assistant to stop, or use the stop control in the chat. This ends the current turn. Anything the assistant already did on the phone stays done; it just does not take any further action.

​

Blockers on the phone

While working on a device, the assistant sometimes runs into something covering the screen that it did not ask for: The assistant never scrolls past or blindly dismisses something it does not recognize. If a login screen appears unexpectedly mid-task, it stops rather than retrying, since the next tap could go somewhere wrong.

​

Related