Add Playwright connection guide under browsers/#461
Draft
robertjamesprior wants to merge 1 commit into
Draft
Conversation
Playwright had no keyword-focused page of its own — it was only covered as one tab in Control and via the separate Playwright Execution page, which are easy to land on by mistake. Add browsers/playwright.mdx covering install, the connectOverCDP URL swap, viewport, stealth, and why to run it on Kernel, with Control linking out to it and reciprocal pointers between the two Playwright pages to disambiguate them. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
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.
Playwright had no page of its own — it was covered only as one tab in Control and via the separate Playwright Execution page.
Why this matters for agents, not just search
Kernel's docs publish an auto-generated
llms.txt— a full index of every doc page with a one-line description, meant for AI coding agents to fetch before acting. Todaybrowser-use,stagehand,magnitude, andnotteare all entries in it; Playwright is not. A developer who tells Claude Code / Cursor "add cloud browser support to my Playwright script" has nothing to fetch — the agent reads the index, finds no Playwright entry, and can't route to a guide.This PR adds the page, so the index gains:
Note: the four framework entries above ship with no description — just link text. This page's
descriptionfrontmatter is keyword-focused (Playwright,cloud browser,CDP), so the entry is actually more matchable than its neighbors. Thedocs.jsonnav entry is what populates the llms.txt line — without it there is no line.Architecture
Keeps Playwright out of
integrations/(it is a CDP client, not a framework layered on top) and gives it a first-class page underbrowsers/, alongsideplaywright-executionandviewport.Changes
browsers/playwright.mdx— framework-guide depth: install, create-a-browser +connectOverCDPURL swap (TS + Python), viewport config, stealth, a "why run Playwright on Kernel" section, next steps.introduction/control.mdx— stays the conceptual overview; the CDP tab and "Going deeper" link out to the new page.<Note>s betweenplaywrightandplaywright-executionso each disambiguates the other (connect-your-own-client vs run-in-the-VM), fixing the naming collision from both directions.docs.json— nav entry in the Intermediate group, beforeplaywright-execution.Method/param names (
connectOverCDP,cdp_ws_url,delete_by_id/deleteByID,stealth,viewport) match existing docs usage. Not previewed locally — Mintlify has no build step;docs.jsonvalidated as JSON.