Anchor

​

Concept mapping

​

Moving the auth setup

1. A connection binds one domain’s authentication state to a named profile.
2. Kernel performs the login — hosted UI, your own UI, or programmatically — and writes the session into that profile.
3. Kernel health-checks the connection and reauthenticates supported flows in the background.
4. Any browser you create with profile: { name } starts logged in, for every domain connected to that profile.

const connection = await kernel.auth.connections.create({
  domain: 'app.example.com',
  profile_name: 'user-8f21c3',
});

const login = await kernel.auth.connections.login(connection.id);
console.log('send the user here:', login.hosted_url);

const browser = await kernel.browsers.create({
  profile: { name: 'user-8f21c3', save_changes: true },
  stealth: true,
});

​

Things to check

• Reauthentication is not universal. Passkey-only flows aren’t supported, and some sites need per-site configuration. See the managed auth FAQ and test your flow before cutting over.
• Health check cadence is per plan. See pricing and limits.
• Concurrency and create rate are separate limits. See concurrency and limits.