Sign-in accounts

Let the tester sign in without a password ever reaching the AI or your test text.

How they work#

A sign-in account is a name, a username and a password stored for a project, for example customer with customer@example.com. Tests refer to it by name ("Sign in as the account \"customer\""), and the tester types the password into the sign-in form itself. The password is encrypted when you save it, never shown again, never returned by the API, and never sent to the AI.

Add one#

• In a project: Sign-in accounts → Add. Fill in the name, username, password and, optionally, the site it belongs to.
• While writing a test: Sign in as… → Add a sign-in account, or, when the plan asks which account to use, + Add a credential. Adding it answers the question.
• Over the API or MCP: add_credential. Through an AI agent the password passes through the agent's own context, so prefer the web app, or the REST API from your secret store.

Use one in a test#

• In the composer, Sign in as… inserts it; the plan lists the accounts it uses under Sign-in accounts.
• In a plain-text test, name it: Sign in as the account "customer", and add it under Show options.
• Over the API: options.credentials: ["customer"], or the plan's credentials.

An account the project does not have is shown as (missing) in the plan.

Delete one#

Deleting an account stops the tests that sign in with it until you add it again or edit them.