Stop treating playwright as the only way to control the page - #568
Merged
Merged
Conversation
process-execution.mdx over-indexed on playwright specifically, when kernel actually exposes four ways to drive a session (computer use, playwright execution, CDP, WebDriver BiDi). Generalize the framing to point at /introduction/control and only name playwright where it's the actual product feature.
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
…t example That example specifically points at the local playwright daemon, so name it directly instead of the generic control-endpoint phrasing.
There was a problem hiding this comment.
Risk assessment: Very Low
Decision: Prior approval stands. Not re-issuing approval.
Re-evaluated after synchronize. The new commit (8e9f3d9) changes one sentence in browsers/process-execution.mdx: it restores the phrase local playwright daemon in the fx co-located agent pattern (replacing generic “local control endpoint” wording). The rest of the PR is still the same Mintlify copy/link edits from the previously approved commit.
Why Very Low (unchanged)
- Documentation-only wording on a single docs page (
+5/−5vsmain) - No application code, APIs, config, CI, or infrastructure files changed
- No auth, billing, schema, or operational impact
- No
CODEOWNERSfile, so codeowner review is not required
Risk did not increase, so the existing approval is not dismissed.
Sent by Cursor Automation: Assign PR reviewers
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
/docs/browsers/process-executionframed playwright as the mechanism for controlling the page, but Kernel actually exposes four control options (computer use, playwright execution, CDP, WebDriver BiDi) — see/introduction/control.Test plan
/introduction/control.Note
Low Risk
Mintlify documentation copy only; no runtime, API, or security behavior changes.
Overview
Updates
browsers/process-executionso page driving is described as browser control rather than Playwright-only.The intro and “when to use process execution” sections now refer to generic page-control calls and steer readers toward all four control paths (Playwright execution, computer use, CDP, WebDriver BiDi), with Playwright kept only where it’s the named product link. The co-located agent pattern still points agents at the local playwright daemon; the port Warning renames that stack piece to the execution API alongside live view and CDP.
Reviewed by Cursor Bugbot for commit 8e9f3d9. Bugbot is set up for automated code reviews on this repo. Configure here.