Move scaling guide to Introduction as "Scale"#442
Conversation
- Move browsers/pools/scaling.mdx to introduction/scale.mdx and retitle to "Scale" - Add it to the Overview nav group and redirect /browsers/pools/scaling to /introduction/scale - Add a "Why reserve browsers with browser pools" section to the pools overview with a backlink to the new page - Update the changelog link to the new path Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using high effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 1495420. Configure here.
| title: "Scaling in Production" | ||
| description: "Recommended practices for scaling" | ||
| title: "Scale" | ||
| description: "Recommended practices for scaling in production" |
There was a problem hiding this comment.
Scale page uses CDP examples
Medium Severity
This PR moves the scaling guide to introduction/scale and lists it under Overview with Create, Control, and Observe, but the architecture accordions still drive browsers only via chromium.connectOverCDP. For intro/overview pages, docs should treat the Playwright Execution API as the default Playwright pattern, like introduction/create and introduction/control.
Triggered by learned rule: Promote Playwright Execution API over direct CDP connections in examples
Reviewed by Cursor Bugbot for commit 1495420. Configure here.
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Risk assessment: Very Low.
Evidence from the diff:
- The change set is documentation-only:
browsers/pools/scaling.mdxis moved tointroduction/scale.mdxwith only title/description frontmatter changes to the moved page. docs.jsonupdates Mintlify navigation and adds a redirect from/browsers/pools/scalingto/introduction/scale.- The remaining edits are a changelog link update, a short browser-pools overview paragraph, and a capitalization fix.
- No application/runtime code, auth or permissions logic, infrastructure, data migrations, shared libraries, or production logic changed.
I found no CODEOWNERS file in the repository. The PR is already approved on the current head commit, so I’m not re-approving it.
Sent by Cursor Automation: Assign PR reviewers
Nudges Mintlify to re-ingest the custom stylesheet; the preview build for this branch was missing it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Risk assessment: Very Low.
Evidence from the current diff:
browsers/pools/scaling.mdxis renamed tointroduction/scale.mdxwith only frontmatter title/description edits; the guide content is otherwise unchanged.docs.jsonupdates Mintlify navigation and adds a redirect from/browsers/pools/scalingto/introduction/scale.- The remaining edits are documentation/link copy in
browsers/pools/overview.mdxandchangelog.mdx, plus a trailing-newline fix instyle.css. - No runtime code, auth/permissions logic, infrastructure, data migrations, shared libraries, or production logic changed.
I found no CODEOWNERS file in the repository. GitHub currently reports the PR as already approved, so I’m leaving this risk assessment as a comment rather than adding another approval.
Sent by Cursor Automation: Assign PR reviewers
juecd
left a comment
There was a problem hiding this comment.
I left a comment about the paragraph but approving so you can merge without another review
|
|
||
| ## Why reserve browsers with browser pools | ||
|
|
||
| Browser pools move browser setup out of your critical path: browsers with your full configuration—stealth, proxies, extensions, profiles—are provisioned ahead of time, so acquiring one returns a ready browser instead of paying setup cost on every task. Reserved browsers aren't billed until they're acquired, so an idle pool costs nothing to keep warm. Because every browser in a pool shares the same configuration, your automation code can acquire and run without per-task setup logic. At high concurrency, pools also give you predictable capacity: a fixed number of browsers is reserved for your workload, independent of on-demand creation. See [Scale](/introduction/scale) for how pools fit into production architecture best practices. |
There was a problem hiding this comment.
I think it's unusual to see long paragraphs like this in doc guides (I cross referenced this intuition with https://modal.com/docs/guide). I would break out each sentence into a bullet.
This sentence doesn't feel specific enough:
Browser pools move browser setup out of your critical path: browsers with your full configuration—stealth, proxies, extensions, profiles—are provisioned ahead of time, so acquiring one returns a ready browser instead of paying setup cost on every task.
Suggestion:
Browser pools move browser setup out of your critical path. It allows you to provision browsers with your specific configuration ahead of time (such as stealth, proxies, extensions, and profiles), rather than the setup latency happening at agent runtime. Acquiring one returns a configured browser in milliseconds.
There was a problem hiding this comment.
Risk assessment: Very Low.
Evidence from the current diff:
browsers/pools/scaling.mdxis moved tointroduction/scale.mdx; the moved page keeps the same guide content with only frontmatter title/description changes.docs.jsonupdates the Mintlify sidebar placement and adds a redirect from/browsers/pools/scalingto/introduction/scale.- The other changes are limited to docs copy/link updates in
browsers/pools/overview.mdxandchangelog.mdx, plus a newline-only fix instyle.css. - No runtime code, auth/permissions logic, infrastructure, data migrations, shared libraries, or production logic changed.
I found no CODEOWNERS file in the repository. GitHub currently reports the PR as already approved, so I’m leaving this assessment as a comment rather than adding another approval. The risk level has not increased, so I’m not dismissing the existing approval.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low.
Evidence from the actual diff:
browsers/pools/scaling.mdxis renamed tointroduction/scale.mdxwith 98% similarity; the moved guide only changes its frontmatter title/description.docs.jsonupdates the Mintlify sidebar and adds a redirect from/browsers/pools/scalingto/introduction/scale.- The remaining edits are docs-only: a short browser-pools overview paragraph, a changelog link update, a capitalization fix, and a trailing-newline fix in
style.css. - No runtime application code, auth/permissions logic, infrastructure, data migrations, shared libraries, or production behavior changed.
I found no CODEOWNERS file in the repository. GitHub already reports this PR as approved, so I’m leaving this risk assessment as a comment rather than adding another approval. The risk level has not increased, so there’s no reason to dismiss an existing approval.
Sent by Cursor Automation: Assign PR reviewers
There was a problem hiding this comment.
Risk assessment: Very Low.
Evidence from the actual diff:
- The PR changes only docs/navigation assets:
browsers/pools/overview.mdx,changelog.mdx,docs.json, a rename frombrowsers/pools/scaling.mdxtointroduction/scale.mdx, and a final-newline touch instyle.css. - The renamed scaling guide is 98% similar to the original and only changes its frontmatter title/description.
docs.jsonmoves the page into the Introduction sidebar and adds a redirect from/browsers/pools/scalingto/introduction/scale.- No runtime code, auth/permissions logic, infrastructure, data migrations, shared libraries, or production application behavior changed.
I found no CODEOWNERS file in the repository. GitHub already reports this PR as approved, so I’m leaving this risk assessment as a comment rather than adding another approval. The latest synchronize event doesn’t increase the risk, so I’m not dismissing the existing approval.
Note: git diff --check flags one trailing space in browsers/pools/overview.mdx, but that doesn’t affect the risk classification.
Sent by Cursor Automation: Assign PR reviewers




Summary
browsers/pools/scaling.mdxtointroduction/scale.mdxso the scaling guide lives in the Overview section alongside Create, Control, and Observe. Page is retitled to Scale.docs.jsonso/browsers/pools/scalingroutes to/introduction/scale.introduction/scaleadded to the Overview group, removed from the Reserved Browsers group./introduction/scalefor production best practices.Testing
Validated
docs.jsonparses as valid JSON and grepped for remaining/browsers/pools/scalingreferences (only the new redirect remains). Did not runmintlify devlocally.Preview: https://tbd-6fc993ce-hypeship-move-scaling-to-intro-scale.mintlify.app/introduction/scale
🤖 Generated with Claude Code
Note
Low Risk
Documentation and navigation-only changes with a redirect; no product or API behavior changes.
Overview
Relocates the production scaling guide from Reserved Browsers to the Overview intro track as
/introduction/scale, retitled Scale, so it sits alongside Create, Control, and Observe.docs.jsonadds a redirect from/browsers/pools/scalingto the new path, listsintroduction/scaleunder Overview, and removesbrowsers/pools/scalingfrom the pools nav group.browsers/pools/overview.mdxrefreshes the page framing (shorter description, examples of pre-configured settings, faster pool acquire vs on-demand create, shared concurrency and billing-until-acquired) and links readers to the Scale guide for production architecture. Fixes capitalization in the release step (“This step is important”).changelog.mdxupdates the January 30 docs bullet to point at/introduction/scale.style.cssadds a trailing newline only.Reviewed by Cursor Bugbot for commit ff99594. Bugbot is set up for automated code reviews on this repo. Configure here.