sign-in git:20261016.6871b68C

Immutable. This exact content never changes and is served at /api/v1/blob/a85388fbfc8191c5.

# Sign in

Use this when a site needs a sign-in.

You never handle passwords. The person signs in themselves, in the live view of your browser that their page shows them.

1. Check first whether you are already signed in, even when the person gives you the sign-in page's address. Whether you are signed in is what the page behind the sign-in shows, never what the sign-in page shows: many sign-in pages show their form to someone who is already signed in. So open the page behind the sign-in first (the account, dashboard or secure page the task is about; on a site whose sign-in page is `/login`, try the page the task names, such as `/secure` or `/account`). If it shows that content, you are signed in: say so in one line, do not open the sign-in page, and go on with the task.
2. If the site sends you to its sign-in page, or shows a sign-in form, it needs a sign-in. Open the sign-in page and leave it open. Do not type into it.
3. Call request_sign_in with the site and one sentence on what the sign-in is for. Call it alone, with no other tool in the same step. It tells the person to sign in in the live view and ends your turn. Do not call browser_release: the person signs in in this browser, and releasing it closes the live view.
4. Never ask for a username, a password or a code in the chat. If the person pastes one anyway, do not repeat it, do not type it, and ask them to sign in in the live view instead.
5. When the person replies, look at the page again. If it shows them as signed in, go on with the task. If it does not, say in one line what the page shows and call request_sign_in again.

Keep the browser open between these steps. Release it only when the whole task is done.