Sessions & HITL

Decide how the agent makes new accounts

Sign up with Google or GitHub (in your order) when the site offers it, the email to register with, and the password — the defaults a sign-up follows for whatever the prompt leaves out.

Get an API key MCP setup

set_new_account_defaults

What it is

The job: Decide what the agent signs up with when you did not say.

`signUpWith` is the ORDERED list of providers a sign-up may take — `["github", "google"]` tries GitHub first, then Google. The run takes the first one the page offers that this workspace can sign in with: a captured session (POST /connect/sessions for the provider’s sign-in host) or a saved login for it. There is no password to keep; the method is remembered for the site so the next sign-in takes the same door. `"password"` or `[]` always fills the form, as does a site that offers none of them.

`email` is the address a sign-up uses when the prompt names none. It should be an inbox you have connected, because most sites confirm a new account by email; the answer reports `emailInboxConnected`, and a run prefers that inbox for its codes. `password` sets the default password; with none, each site gets its own strong generated one, readable afterwards with reveal_account. A method, email or password in the prompt always wins.

The call

Call it exactly like this.

Copied from the tool's registration and the route handler — not paraphrased.

MCPset_new_account_defaults.mcp.jsonjson

// MCP tool call — server "twin-browser"
{
  "tool": "set_new_account_defaults",
  "arguments": {
    "signUpWith": ["github", "google"],
    "email": "signups@example.com"
  }
}

PUT /api/v1/accounts/signup-defaultsrequest.shbash

curl -X PUT https://twin-browser.com/api/v1/accounts/signup-defaults \
  -H "Authorization: Bearer $TWIN_API_KEY" \
  -H "content-type: application/json" \
  -d '{"providers":["github","google"],"email":"signups@example.com"}'

With “save secrets automatically” turned off for the workspace, no password is generated — a password nobody keeps is one nobody holds — so a sign-up without a default password asks for one instead.

Parameters accepted by set_new_account_defaults
Parameter	Type	What it does
signUpWith	string[] \| "password"	Ordered providers ("google", "github") to sign up with when offered and usable; "password" or [] always fills the form.
email	string \| null	Default address for new accounts; null clears it.
password	string	Default password, 8–128 characters (PUT /accounts/new-account-password).
clearPassword	boolean	Remove the default password: each site gets a generated one.

Returns

response.jsonjson

{ "defaults": { "providers": [
                  { "id": "github", "on": true, "ready": true, "session": true, "login": false },
                  { "id": "google", "on": true, "ready": false, "session": false, "login": false } ],
                "email": "signups@example.com", "emailInboxConnected": true },
  "password": { "set": false, "whenUnset": "generated per site" } }