Make browser profiles first-class in guides

[AnnaXWang]

Summary

• move the canonical Browser Profiles guide from /auth/profiles to /browsers/profiles
• add focused guides for saving state, concurrency, and AI agent patterns
• promote Profiles, Auth, and Vaults to peer navigation groups while retaining the Auth label
• redirect every historical Profiles route, including the former /profiles/overview and /profiles/managed-auth/* hierarchy
• redirect browser and generated .md URLs and preserve historical deep-link anchors
• update internal links and improve Profiles discovery from the browser creation guide

The docs homepage is unchanged.

Why

Profiles persist browser state across agent runs independently of Managed Auth. The guide hierarchy now reflects that product relationship and documents the snapshot, writer, and browser-pool constraints directly.

Validation

• mintlify validate
• mintlify broken-links
• hosted Mintlify deployment passed
• tested all 18 historical browser and .md routes: each resolves to its expected canonical destination in one redirect and returns 200
• verified all 13 historical deep-link anchors render on the canonical Profiles page
• verified all four Profiles pages and the generated Markdown page return 200 directly

---

Note

Low Risk
Documentation-only restructure with redirects and link updates; no runtime or API behavior changes.

Overview
This PR repositions Browser Profiles as a first-class browsers concern instead of living under Managed Auth.

The monolithic /auth/profiles guide is removed and replaced by /browsers/profiles plus three focused pages: Save and reuse state, Sharing and concurrency, and Patterns for AI agents. The new overview frames profiles as independent of Managed Auth, adds primitive-selection guidance, and preserves historical deep-link anchors via span IDs on the canonical pages.

Navigation and routing promote Profiles, Auth, and Vaults as peer groups in docs.json, with redirects from /auth/profiles, /profiles/*, and the old /profiles/managed-auth/* tree. Internal links across auth, browsers, integrations, changelog, CLI reference, and introduction are updated to /browsers/profiles (and new subpaths such as Reuse one identity across sites). Auth docs now point at Browser Profiles for where session state is stored.

^{Reviewed by Cursor Bugbot for commit e2d62a7. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Sep 16, 2026, 12:06 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[cursor]

Stale comment

Risk assessment: Very Low

Decision: Do not re-approve. Prior approval on a2094dc still stands. Risk did not increase. No CODEOWNERS file exists, and the main branch ruleset does not require code owner review.

Re-evaluated the current diff against main (35 files, +759/−643). All changes are Mintlify documentation and site config:

• Deletes auth/profiles.mdx and adds browsers/profiles.mdx plus three guide pages (save-and-reuse, concurrency, agent-patterns)
• Updates docs.json navigation so Profiles, Auth, and Vaults are peer sidebar groups
• Adds static redirects from historical /auth/profiles and /profiles* paths to existing internal docs routes
• Retargets internal links and changelog references on existing .mdx pages

Why Very Low

• No application, API, auth, billing, CI/workflow, or infrastructure code changed
• No production logic or shared-service behavior change
• Redirect destinations are internal docs paths, not new external targets
• New pages are product documentation with SDK/API examples, not model-instruction or prompt files
• Blast radius is limited to docs content, sidebar IA, and static redirects

Residual risk is limited to a broken docs link or a mis-aimed redirect, which stays on the docs site.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Stale comment

Risk assessment: Very Low

Decision: Do not re-approve. Prior approval on a2094dc still stands. Risk did not increase after 0c24757 (merge of main). No CODEOWNERS file exists, and the main branch ruleset does not require code owner review.

Re-evaluated the current diff against main (35 files, +759/−643). All changes are Mintlify documentation and site config:

• Deletes auth/profiles.mdx and adds browsers/profiles.mdx plus three guide pages (save-and-reuse, concurrency, agent-patterns)
• Updates docs.json navigation so Profiles, Auth, and Vaults are peer sidebar groups
• Adds static redirects from historical /auth/profiles and /profiles* paths to existing internal docs routes
• Retargets internal links and changelog references on existing .mdx pages

The new merge commit only resolves a docs.json conflict by keeping this PR's navigation and inserting config-registry from main. It does not add application, API, or infrastructure changes.

Why Very Low

• No application, API, auth, billing, CI/workflow, or infrastructure code changed
• No production logic or shared-service behavior change
• Redirect destinations are internal docs paths, not new external targets
• New pages are product documentation with SDK/API examples, not model-instruction or prompt files
• Blast radius is limited to docs content, sidebar IA, and static redirects

Residual risk is limited to a broken docs link or a mis-aimed redirect, which stays on the docs site.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Stale Bugbot comment from a previous run.

[cursor]

Relative API reference link

Medium Severity

The Profiles API reference link uses a relative /api-reference/profiles/list-profiles path. Those pages are generated from the remote OpenAPI spec and have no local .mdx files, so relative links fail mint broken-links. The previous Profiles guide used the absolute https://kernel.sh/docs/api-reference/... URL.

 

^{Triggered by learned rule: Use absolute URLs for /api-reference/ links}

^{Reviewed by Cursor Bugbot for commit 0c24757. Configure here.}

[AnnaXWang]

these two PRs are dependent:

• https://github.com/kernel/kernel/pull/4079
• Update browser profiles documentation links cookbooks#4

[cursor]

Risk assessment: Very Low

Decision: Do not re-approve. Prior approval on a2094dc still stands. Risk did not increase after e2d62a7. No CODEOWNERS file exists, and the main branch ruleset does not require code owner review.

Re-evaluated the current diff against main (35 files, +775/−643). All changes are Mintlify documentation and site config:

• Deletes auth/profiles.mdx and adds browsers/profiles.mdx plus three guide pages (save-and-reuse, concurrency, agent-patterns)
• Updates docs.json navigation so Profiles, Auth, and Vaults are peer sidebar groups
• Adds static redirects from historical /auth/profiles and /profiles* paths to existing internal docs routes
• Retargets internal links and changelog references on existing .mdx pages

The new commit (e2d62a7) only adds documentation guidance recommending one profiled browser with multiple tabs for concurrent same-user work. It does not add application, API, or infrastructure changes.

Why Very Low

• No application, API, auth, billing, CI/workflow, or infrastructure code changed
• No production logic or shared-service behavior change
• Redirect destinations are internal docs paths, not new external targets
• New pages are product documentation with SDK/API examples, not model-instruction or prompt files
• Blast radius is limited to docs content, sidebar IA, and static redirects

Residual risk is limited to a broken docs link or a mis-aimed redirect, which stays on the docs site.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.

There are 2 total unresolved issues (including 1 from previous review).

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit e2d62a7. Configure here.}

[cursor]

Playwright treated as the only path

Medium Severity

The new tabs guidance presents Playwright's context.newPage() as the way to open tabs and links only to Playwright Execution. Kernel has four page-control paths, and other guides use generic browser-control wording that points at /introduction/control.

 

^{Triggered by learned rule: Four control paths; don't treat Playwright as the only way}

^{Reviewed by Cursor Bugbot for commit e2d62a7. Configure here.}