docs(mcp): execute_playwright_code passthrough + manage_replays tool

[dprevoznik]

Updates the MCP server docs to match the new tool behavior in kernel-mcp-server (server-side change already merged).

What changed

• execute_playwright_code — rewritten as a thin passthrough. session_id is now required; the tool no longer creates a browser when it's omitted, no longer deletes the browser afterward, and no longer returns a replay_url. Added a note steering callers to manage_browsers for lifecycle and updated the example (input includes session_id, output drops replay_url).
• manage_replays — new tool page documenting the start / stop / list actions and the framerate, max_duration_in_seconds, record_audio start params. Added to the Tools nav in docs.json.
• manage_browsers — added a line noting browser lifecycle lives here (create before execute, delete when done).
• Examples — the Playwright example now shows create → execute → delete; added a "record a video replay" example using manage_replays.
• browsers/playwright-execution.mdx — reworded the MCP integration blurb (no longer "automatic video replay and cleanup").

Notes

• Param descriptions for manage_replays are inferred from the PR summary; worth a skim against the tool's live schema before publishing.
• Docs-only change; docs.json validates as JSON. No preview build run.

---

Note

Low Risk
Documentation-only updates with no runtime or security impact; main risk is minor inaccuracy in inferred manage_replays param descriptions until verified against the live schema.

Overview
Aligns MCP docs with kernel-mcp-server behavior: execute_playwright_code is documented as a thin VM passthrough with required session_id, no implicit create/delete, and no replay_url in responses; lifecycle is explicitly manage_browsers (create → execute → delete).

Adds a manage_replays reference page (start / stop / list, headful-only note) and wires it into docs.json nav. manage_browsers and MCP examples now show the create/execute/delete flow plus an opt-in replay recording example; playwright-execution.mdx drops “automatic video replay and cleanup” wording.

^{Reviewed by Cursor Bugbot for commit d36173f. Bugbot is set up for automated code reviews on this repo. Configure here.}

[mintlify]

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

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Jul 21, 2026, 2:36 AM

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

[cursor]

Risk assessment: Very Low

The current diff changes six Mintlify documentation/navigation files only: it documents the required browser-session lifecycle, adds the manage_replays reference page and navigation entry, and updates examples. It does not change executable production code, infrastructure, authentication, permissions, or security boundaries. The update since the prior approval only removes the framerate field from one JSON example, so risk has not increased. No CODEOWNERS file is present, and the PR is already approved, so I am retaining the existing approval without submitting another one.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

The diff is limited to six Mintlify documentation/navigation files (64 additions, 8 deletions): it updates MCP usage examples and lifecycle guidance, adds the manage_replays reference page, and adds that page to docs.json. It changes no executable code, infrastructure, authentication, permissions, or security boundary, so the blast radius is limited to published documentation. The only commit after the existing approval removes one framerate field from a JSON example, which does not increase risk. No CODEOWNERS file is present. The PR is already approved, so I did not submit another approval or revoke the existing one.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[mintlify]

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

Project	Status	Preview	Updated (UTC)
Kernel	🟡 Building	–	Jul 21, 2026, 2:35 AM

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

[cursor]

Risk assessment: Very Low

The current diff is limited to six Mintlify documentation and navigation files (68 additions, 8 deletions). It updates MCP workflow guidance and examples, adds the manage_replays reference page, and adds that page to docs.json; it changes no executable code, infrastructure, authentication, permissions, or security boundary.

Since the existing approval, the only changes split one dense workflow sentence into bullets and remove framerate from one JSON example. These edits don't increase risk. No CODEOWNERS file is present, and the PR is already approved, so I did not submit another approval or revoke the existing one.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

The full diff is limited to six Mintlify documentation and navigation files (64 additions, 8 deletions). It adds the manage_replays reference and navigation entry and updates MCP examples and browser-session guidance. No executable code, infrastructure, authentication, permissions, or security boundaries change, so the blast radius is limited to published documentation.

Since the previous assessment, commit d36173f only replaces a three-item workflow paragraph with a shorter execute_playwright_code description in one documentation page (1 addition, 5 deletions). This does not increase risk. No CODEOWNERS file is present, and the PR is already approved, so I did not submit another approval or revoke the existing one.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

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 d36173f. Configure here.}

[cursor]

Missing canonical replays link

Low Severity

The new manage_replays page restates replay recording behavior (opt-in start/stop/list flow and headful limits) without linking to the canonical /browsers/replays guide for full details such as replay_view_url and download. This violates the single-source-of-truth rule that cross-page coverage should summarize and link rather than stand alone.

 

^{Triggered by learned rule: Single source of truth — no deep content duplication across pages}

^{Reviewed by Cursor Bugbot for commit d36173f. Configure here.}