Document acquire-time profile binding for browser pools

[robertjamesprior]

Summary

Browser pools support loading a profile at acquire time, but only the changelog mentions it. The two guide pages that cover per-user pool profiles still teach the two-call flow — acquire, then browsers.update — and the CLI reference doesn't list the flags the CLI already has.

This documents the acquire-time path as the default:

• browsers/pools.mdx — the per-user profiles section now binds the profile on the acquire call, with TypeScript/Python/Go examples updated. Notes that the profile loads before the browser is returned, that save_changes still applies, and that reuse doesn't (the lease always destroys the browser). Links to the post-create path for the case where a profile has to be attached to an already-running browser.
• browsers/profiles/concurrency.mdx — the per-user steps collapse from four to three.
• browsers/profiles/save-and-reuse.mdx — cross-link from "Load a profile after browser creation" to the acquire-time path.
• reference/cli/browser-pools.mdx — adds --profile-id, --profile-name, and --save-changes to acquire, and notes that --reuse doesn't apply to a lease carrying an acquire-time profile.

Validation

mint broken-links is the only CI check on this repo and no separate lint/build step exists; both anchors added here already exist and are referenced elsewhere in the docs. No preview run.

Not in this PR

Two adjacent gaps I noticed and left alone:

• The acquire flag table is also missing --name, --start-url, --tag, --telemetry, and --telemetry-cdp-exclude, which the CLI accepts today.
• The MCP manage_browser_pools tool has no profile parameter on acquire, so its reference correctly omits one. API/CLI parity for MCP would be a separate change.

[mintlify]

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

Project	Status	Preview	Updated
Kernel	🟢 Ready	View Preview	Oct 5, 2026, 3:41 PM

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