wizardlisted

# Hand the work back cleanly Some steps are not yours to take. When one appears, the failure mode is not getting it wrong — it is not noticing, and retrying instead. ## The measurement this exists for 2026-08-19, one session on this machine: a browser call returned *"Multiple Chrome browsers are connected to this account and none has been selected. Before any browser action, you MUST call the AskUserQuestion tool."* The session retried browser calls against that message from **10:14 to 12:24** — two hours and ten minutes — and never asked. The error had named the remedy in its own text. That is the whole class. The message is accurate, it names a human, and every retry fails identically because nothing about the situation changed. ## Recognise it You are blocked on a human when any of these is true: - The error names a **choice** ("none has been selected", "multiple accounts"). - It names a **permission or grant** you cannot issue yourself. - It asks for a **credential**. You must never enter one anyway — see below. - It requires a **physical or out-of-band act**: plug in a device, click a link in an email, approve a push notification, flip a setting in a console you have no API for. - The identical call has failed twice with byte-identical output. Two is the signal; there is no information in a third. Distinguish it from a hang or a flake. A frozen renderer, a timeout, a 502 — those are worth one retry. A decision is not. ## Stop, then write the steps **Stop