docs: note computer controls screenshots are faster for webgl

[masnwilliams]

Summary

• Add a tip under Take screenshots in computer-controls.mdx noting that computer controls captureScreenshot is faster than CDP Page.captureScreenshot on WebGL and animation-heavy pages — relevant for customers driving computer-use loops off screenshots.
• Add a note on gpu-acceleration.mdx clarifying that GPU speeds up page rendering, not CDP screenshot capture (a common misconception).

Kept the guidance qualitative rather than publishing specific ms numbers — single-page synthetic benches age badly and customers tend to cite absolute figures back.

Test plan

• Preview renders <Tip> and <Note> callouts
• Cross-links resolve between the two pages

---

Note

Low Risk
Low risk documentation-only change that adjusts performance guidance and cross-links between pages; no runtime or API behavior is modified.

Overview
Adds a <Tip> to computer-controls.mdx noting that computer controls captureScreenshot is faster than CDP Page.captureScreenshot on WebGL/animation-heavy pages, and that GPU acceleration provides only a small additional boost for computer-controls screenshots.

Adds a <Note> to gpu-acceleration.mdx clarifying that GPU acceleration improves rendering performance but does not reduce CDP screenshot latency, and links back to the computer controls screenshot guidance.

^{Reviewed by Cursor Bugbot for commit 9894264. 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	Apr 23, 2026, 10:16 PM

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

[firetiger-agent]

Firetiger deploy monitoring skipped

This PR didn't match the auto-monitor filter configured on your GitHub connection:

Any PR that changes the kernel API. Monitor changes to API endpoints (packages/api/cmd/api/) and Temporal workflows (packages/api/lib/temporal) in the kernel repo

Reason: This PR only modifies documentation files (computer-controls.mdx and gpu-acceleration.mdx) and does not change any kernel API endpoints or Temporal workflows.

To monitor this PR anyway, reply with @firetiger monitor this.

[cursor]

Stale comment

Risk assessment: Very Low.

The current diff only adds short documentation callouts in browsers/computer-controls.mdx and browsers/gpu-acceleration.mdx. There are no codepath, config, infrastructure, schema, prompt, or navigation changes, and the blast radius is limited to rendered docs content. I found no CODEOWNERS file requiring separate owner review.

The PR already has an approval, so I’m not adding another approval. The update does not increase risk, so no approval dismissal is needed.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low.

The diff only adds short documentation callouts in browsers/computer-controls.mdx and browsers/gpu-acceleration.mdx about screenshot performance and GPU acceleration scope. There are no codepath, config, navigation, infrastructure, schema, prompt, or security-boundary changes, and the blast radius is limited to rendered docs content.

I found no CODEOWNERS file requiring separate owner review. The PR is already approved at the current head, so I’m not adding another approval. The update does not increase risk, so no approval dismissal is needed.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Cursor Bugbot has reviewed your changes 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 9894264. Configure here.}

[cursor]

Documents Chromium CDP behavior as product spec

Low Severity

The statement "CDP's Page.captureScreenshot latency is unaffected by GPU" documents a Chromium internal behavior as a product-level fact. This violates the rule to keep feature descriptions at the product level rather than describing what Chromium does under the hood — this behavior could change across Chromium versions. The guidance in computer-controls.mdx similarly characterizes CDP screenshot internals. Both notes can convey the same user guidance (prefer computer controls for screenshot-heavy loops) without asserting specifics about CDP's internal capture path.

Additional Locations (1)

• browsers/computer-controls.mdx#L160-L163

 

^{Triggered by learned rule: Don't document Chromium internals as product specs}

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