Skip to main content
A build signs in to the website only when its task needs an account. For saving logins, see Logins.

​
When a build signs in

A read build tries its task signed out first. It signs in only when the task needs an account or the site shows a sign-in wall, and the finished tool then requires a login. A tool built signed out never does. A write or ask build given a login signs in before anything else. To make a read build sign in first, set force_sign_in to true; the tool then always signs in.

​
Which login it uses

  1. A login you name: pass login_id to use one saved login.
  2. The site’s saved login: the build uses the one saved login, or asks which when several could sign in.
  3. A login the person enters: with none saved, the job asks on its answer page, which can save the login too.
Never ask for a password in chat. When the job asks for a login, give the person its answer_url and keep waiting. See Answer a job’s questions.

​
When the website rejects a login

The job reports needs_input with the error credentials_rejected, and waits up to 60 minutes for someone who can edit that login to correct it. It then resumes as the same job; don’t start the build again.
  • You can pass a login inline instead, but its values pass through your client and its model provider. The answer page keeps them out of the conversation.
  • A build that may have changed the website before its login was rejected says so with error.details.possible_commit. When it resumes, it checks the website first and never repeats a change that happened.
  • Sign-in codes are covered in two-factor sign-in.