Skip to content

Add Browser REPL guide - #613

Merged
dprevoznik merged 10 commits into
mainfrom
hypeship/browser-repl-guide
Sep 23, 2026
Merged

dprevoznik merged 10 commits into
mainfrom
hypeship/browser-repl-guide

Conversation

@dprevoznik

@dprevoznik dprevoznik commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Adds browsers/repl.mdx, a guide for the persistent Browser REPL API, following the same format as the Playwright Execution guide (how it works, quick example across TS/Python/Go/CLI, helpers, timeouts, error handling, use cases).
  • Covers what's specific to REPL: persistence across calls, the browser-control helper surface, WebMCP/Patchright/Playwright-core integration, reset/timeout behavior, the lifecycle/failure-semantics table, the security model (unrestricted code execution, not sandboxed), and a comparison section on when to reach for REPL vs Playwright Execution.
  • Wires the new page into docs.json under Guides → Working with your browser → Intermediate, next to Playwright Execution and WebMCP.

Testing

  • Verified docs.json is valid JSON and all internal links (/browsers/webmcp, /browsers/playwright-execution, /browsers/process-execution, /apps) resolve to existing pages.
  • Did not run the Mintlify dev server to render the page locally — no build/lint tooling was available in this environment.

🤖 Generated with Claude Code


Note

Low Risk
Documentation-only changes with a nav entry in docs.json; no runtime or API behavior is modified.

Overview
Adds a new Browser REPL guide at browsers/repl.mdx and registers it in docs.json under Guides → Working with your browser → Intermediate (alongside Playwright Execution and WebMCP).

The page documents the persistent in-VM Node REPL: how calls retain top-level state across cells, CLI/TS/Python/Go usage, browser-control and WebMCP helpers, optional patchright/playwright-core and global npm installs via process exec, explicit output channels (repl.write, console, screenshots), timeout_sec/reset, lifecycle and failure semantics (repl_id, destructive timeouts), error fields, and the unrestricted RCE security model with agent-oriented use cases (multi-step loops, accessibility snapshots, iframe CDP targets).

Reviewed by Cursor Bugbot for commit 507c0e9. Bugbot is set up for automated code reviews on this repo. Configure here.

Adds a guide for the persistent Browser REPL API, modeled on the
Playwright Execution guide, covering persistence semantics, browser
control helpers, WebMCP/Patchright/Playwright integration, timeout and
reset behavior, lifecycle/failure semantics, the security model, and
when to reach for it over Playwright Execution.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@mintlify

mintlify Bot commented Sep 21, 2026

Copy link
Copy Markdown
Contributor

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

Project Status Preview Updated
Kernel 🟢 Ready View Preview Sep 23, 2026, 1:17 AM

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

cursor[bot]
cursor Bot approved these changes Sep 21, 2026
The persistence example never navigated anywhere and assumed a search
box/main landmark that didn't exist on any specific page; the
accessibility-snapshot example raced Wikipedia's own late-loading
banner and intermittently missed the Search button. Both now navigate
to a real page and wait for load before acting, verified against a
live browser session.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale comment

Risk Assessment: Very Low

Decision: Prior approval stands (not re-approved).

Re-evaluated after the latest push (58370cc). Risk is unchanged.

This PR still only adds a Mintlify docs page (browsers/repl.mdx) and a single sidebar entry in docs.json. There is no application, SDK, CI, auth, or infrastructure change.

Evidence

  • Files: browsers/repl.mdx (new user-facing guide) and one navigation path in docs.json
  • Incremental update: Two example snippets now navigate to a real page, wait for load, and use more reliable selectors. Still documentation-only.
  • Blast radius: Public documentation site only; no production logic, shared services, or runtime codepaths
  • Complexity: Content and nav wiring; no behavioral or schema changes
  • CODEOWNERS: None present; no ownership review required

Why not higher

User-facing docs expand the site, but the change remains documentation-only with no operational or security-model impact on the product itself.

Re-approval

Previously approved as Very Low on 8cd7c23. The follow-up commit does not increase risk, so approval is left in place and is not submitted again.

Recommendation: Safe to merge from a risk perspective.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale comment

Risk Assessment: Very Low

Decision: Prior approval stands (not re-approved).

Re-evaluated after the latest push (7b71871). Risk is unchanged.

This PR still only adds a Mintlify docs page (browsers/repl.mdx) and a single sidebar entry in docs.json. There is no application, SDK, CI, auth, or infrastructure change.

Evidence

  • Files: browsers/repl.mdx (new user-facing guide) and one navigation path in docs.json
  • Incremental update: Removes the “Browser REPL vs Playwright Execution” comparison section. Still documentation-only; surface area is slightly smaller, not larger.
  • Blast radius: Public documentation site only; no production logic, shared services, or runtime codepaths
  • Complexity: Content and nav wiring; no behavioral or schema changes
  • CODEOWNERS: None present; no ownership review required

Why not higher

User-facing docs expand the site, but the change remains documentation-only with no operational or security-model impact on the product itself.

Re-approval

Previously approved as Very Low on 8cd7c23. The follow-up commits do not increase risk, so approval is left in place and is not submitted again.

Recommendation: Safe to merge from a risk perspective.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale comment

Risk Assessment: Very Low

Decision: Prior approval stands (not re-approved).

Re-evaluated after the latest push (653b385, merge of main into this branch). Risk is unchanged.

This PR still only adds a Mintlify docs page (browsers/repl.mdx) and a single sidebar entry in docs.json. There is no application, SDK, CI, auth, or infrastructure change.

Evidence

  • Files: browsers/repl.mdx (new user-facing guide) and one navigation path in docs.json
  • Incremental update: Merge of main (#614 accessibility-snapshot docs). The PR-unique three-dot diff is still the same two documentation files; no new codepaths were introduced by this branch.
  • Blast radius: Public documentation site only; no production logic, shared services, or runtime codepaths
  • Complexity: Content and nav wiring; no behavioral or schema changes
  • CODEOWNERS: None present; no ownership review required

Why not higher

User-facing docs expand the site, but the change remains documentation-only with no operational or security-model impact on the product itself.

Re-approval

Previously approved as Very Low on 8cd7c23. The follow-up commits, including this merge from main, do not increase risk, so approval is left in place and is not submitted again.

Recommendation: Safe to merge from a risk perspective.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@dprevoznik
dprevoznik requested a review from rgarcia September 21, 2026 16:31

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk Assessment: Very Low

Decision: Prior approval stands (not re-approved).

Re-evaluated after the latest push (1cb7e4b, merge of main into this branch). Risk is unchanged.

This PR still only adds a Mintlify docs page (browsers/repl.mdx) and a single sidebar entry in docs.json. There is no application, SDK, CI, auth, or infrastructure change.

Evidence

  • Files unique to this branch: browsers/repl.mdx (new user-facing guide, +390) and one navigation path in docs.json
  • Incremental update: Merge of main (#617, a Val Town guide link). The only file that changed since the last assessment is integrations/valtown.mdx, which is already on main and is not part of this PR's diff against main.
  • Blast radius: Public documentation site only; no production logic, shared services, or runtime codepaths
  • Complexity: Content and nav wiring; no behavioral or schema changes
  • CODEOWNERS: None present; no ownership review required

Why not higher

The new page is published product documentation, not an instruction file that changes model or product behavior. It does not alter auth, permissions, or any runtime codepath.

Re-approval

Previously approved as Very Low on 8cd7c23. This merge from main does not increase risk, so approval is left in place and is not submitted again.

Recommendation: Safe to merge from a risk perspective.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Fix All in Cursor

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

Want higher recall? High effort reviews run extra passes and find more bugs. A team admin can switch effort levels in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 1cb7e4b. Configure here.

Comment thread browsers/repl.mdx
@dprevoznik
dprevoznik requested a review from rgarcia September 22, 2026 00:40

@rgarcia rgarcia left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thank you very much for writing this!

Comment thread browsers/repl.mdx Outdated
Comment thread browsers/repl.mdx Outdated
Comment thread browsers/repl.mdx
Comment thread browsers/repl.mdx Outdated
- Reword frontmatter description away from "persistent JavaScript"
- Lead CodeGroups with the CLI example, matching Raf's instinct
- Link to the WebMCP guide where webmcp is first introduced, not just
  at the end of the section

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk Assessment: Very Low

Decision: Prior approval stands. This update is not a new approval.

Re-evaluated after 67b19a7 ("Address Raf's review comments"). Risk is unchanged from the earlier approval.

Evidence

  • Files: browsers/repl.mdx (new Mintlify guide) and one sidebar entry in docs.json. The latest commit changes only browsers/repl.mdx (+10 / −10): frontmatter wording, CLI-first code samples, and a WebMCP doc link.
  • Codepaths: No application, SDK, API, auth, billing, or infrastructure code. docs.json only adds the page to the existing Intermediate guides group.
  • Blast radius: Published documentation content. No shared runtime, permissions, or production logic.
  • Prompt override: browsers/repl.mdx is a product guide rendered by Mintlify, not an LLM instruction file or system prompt.

No CODEOWNERS file is present, so code-owner review is not required by the repo. Approval is not repeated because this automation already approved the PR.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Adds the npm-install-and-import example Raf asked for (cheerio +
httpGet, verified live), and documents a real failure mode found while
testing: npm install -g can fail with UNABLE_TO_VERIFY_LEAF_SIGNATURE
on some images, fixed by passing NODE_OPTIONS=--use-openssl-ca to the
install command.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk Assessment: Very Low

Decision: Prior approval stands. This update is not a new approval.

Re-evaluated after 463ddf8 (section rename and custom npm install docs) and the follow-up merge of main (f192776). Risk is unchanged from the earlier approval.

Evidence

  • Files unique to this PR: browsers/repl.mdx (new Mintlify guide, +408) and one sidebar entry in docs.json. The latest content commit changes only browsers/repl.mdx (+21 / −3): it renames the libraries section and adds a documented npm install -g plus dynamic import example.
  • Codepaths: No application, SDK, API, auth, billing, or infrastructure code. docs.json only adds browsers/repl to the existing Intermediate guides group.
  • Blast radius: Published documentation content. No shared runtime, permissions, or production logic.
  • Prompt override: browsers/repl.mdx is a product guide rendered by Mintlify, not an LLM instruction file or system prompt.

No CODEOWNERS file is present, so code-owner review is not required by the repo. Approval is not repeated because this automation already approved the PR.

Recommendation: Safe to merge from a risk perspective.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk Assessment: Very Low

Decision: Prior approval stands. This update is not a new approval.

Re-evaluated after 09c4b68 ("Move npm cert-verification note into an Info box, generalize wording"). Risk is unchanged from the earlier approval.

Evidence

  • Files vs main: browsers/repl.mdx (new Mintlify guide) and docs.json (one sidebar entry, browsers/repl, next to the other browser pages).
  • Latest commit: Moves the npm UNABLE_TO_VERIFY_LEAF_SIGNATURE note into an <Info> box and generalizes the sentence above the existing install example. Copy and formatting only.
  • Blast radius: Published product documentation and navigation. No application code, SDK, auth, permissions, CI, infrastructure, or schema changes.
  • browsers/repl.mdx is a user-facing docs page, not an agent instruction or system prompt.
  • No CODEOWNERS file, so code owner review is not required.

Risk remains Very Low. Approval is left in place.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk Assessment: Very Low

Decision: Prior approval stands. This update is not a new approval.

Re-evaluated after 507c0e9 ("Drop NODE_OPTIONS from the main install command, keep it in the Info box"). Risk is unchanged from the earlier approval.

Evidence

  • Files vs main: browsers/repl.mdx (new Mintlify guide, +412) and docs.json (one sidebar entry, browsers/repl, in the existing Intermediate guides group).
  • Latest commit: One-line edit in browsers/repl.mdx. The main npm install -g cheerio example no longer passes --env NODE_OPTIONS=--use-openssl-ca. The existing Info box still describes that workaround. Copy only.
  • Blast radius: Published product documentation and navigation. No application code, SDK, auth, permissions, CI, infrastructure, or schema changes.
  • browsers/repl.mdx is a user-facing docs page, not an agent instruction or system prompt.
  • No CODEOWNERS file, so code owner review is not required.

Risk remains Very Low. Approval from this automation on 8cd7c23 is left in place.

Recommendation: Safe to merge from a risk perspective.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

@dprevoznik
dprevoznik merged commit 93bc584 into main Sep 23, 2026
4 checks passed
@dprevoznik
dprevoznik deleted the hypeship/browser-repl-guide branch September 23, 2026 01:23

This branch was successfully deployed

1 active deployment
staging 507c0e9b Deployed Sep 23, 2026 by mintlify[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants