Document the platform category and correct control's sensitivity

[archandatta]

Summary

Docs half of the browser-telemetry control / platform split (kernel-images#322, kernel-images#323, kernel#3086). Two things on this page stop being true when that ships, one of them in a way that matters for compliance.

• control narrows. It was "computer-control API calls against the session" and in practice every in-VM API endpoint. It is now the actions that drive the browser — computer controls, Playwright execution, screenshots, clipboard — plus cdp_command for browser-control commands sent over the CDP proxy.
• platform is new, opt-in, and carries the VM-management traffic that used to sit in control (recording lifecycle, filesystem, process, telemetry and browser configuration). Documented with when you'd actually want it: debugging a profile save or a replay rather than the agent.
• The sensitivity table was wrong once code landed. It grouped control with the categories that carry "session metadata only ... no page content", and api_call now carries the source submitted for Playwright execution — in a category that is on by default. The row now says so, notes the 8 KB clip, and states what cdp_command deliberately does not capture (typed text, key names, navigation URLs — only the character count).
• Actionable guidance rather than just a warning: pass credentials into Playwright snippets through variables instead of as literals, so the captured source doesn't carry them. Same note added to the BAA warning, since control stays available to BAA orgs when network / console / screenshot don't.

The default-set description on the overview page is unchanged and still correct — the default set is still control, connection, system, captcha.

Sequencing

Should merge with or just after the kernel-images release and kernel#3086, not before: until then platform isn't selectable and control still carries the platform traffic.

Notes

Left formatting alone — this file doesn't currently satisfy prettier at baseline and CI only checks broken links, so running it would bury the change in reflowed tables. No new links added.

Review round

Three accuracy fixes after checking every claim against the generated operation-to-category map and the emitting code:

• The platform row omitted three operations it covers: log streaming and both scale-to-zero calls. Added.
• "clipped to 8192 characters" was wrong — the cap is 8 KB of bytes, trimmed to a character boundary. Now reads 8 KB, and both API specs were corrected to say bytes.
• "one action reads as one event" overstated the phase collapsing: a click is still a press and a release. Reworded, and the named-key explanation now matches the allowlist the code actually uses rather than a character-count rule.

[mintlify]

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

Project	Status	Preview	Updated (UTC)
Kernel	🟢 Ready	View Preview	Aug 4, 2026, 1:20 PM

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

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
docs	Error		Aug 7, 2026 12:35pm

[cursor]

Stale comment

Risk assessment: Very Low

Verdict: No action needed — prior approval remains valid (risk did not increase).

Re-evaluation after synchronize

Previous automation approval was on 778a23a9. Current head is 32687ed. Re-assessed the updated diff.

Evidence (from diff)

• 1 file changed: browsers/telemetry/categories.mdx (+15 / −5)
• Documentation-only MDX update: revises the control category description, documents a new platform category, and corrects the data-sensitivity table / guidance around Playwright code capture and CDP command redaction
• No application logic, APIs, auth, infra, config, or schema changes
• No CODEOWNERS file present

Risk factors

Factor	Assessment
Codepaths modified	Docs content only
Blast radius	Readers of telemetry category docs
Complexity	Low — prose/table updates
Infrastructure impact	None
Operational / security risk	None in code; content clarifies sensitivity semantics

Decision

Still meets Very Low criteria (documentation-only, small scoped diff, no production logic or shared-system changes). Risk is unchanged from the prior approval, so approval is not revoked and the PR is not re-approved.

  

_{Sent by Cursor Automation: Assign PR reviewers}

[cursor]

Risk assessment: Very Low

Verdict: No action needed — prior approval remains valid (risk did not increase).

Re-evaluation after synchronize

Previous automation approval was on 778a23a9. Current head is 10591a04. Re-assessed the updated diff.

Evidence (from diff)

• 1 file changed: browsers/telemetry/categories.mdx (+15 / −5)
• Documentation-only MDX update: revises the control category description, documents a new platform category, and corrects the data-sensitivity table / guidance around Playwright code capture and CDP command redaction
• No application logic, APIs, auth, infra, config, or schema changes
• No CODEOWNERS file present

Risk factors

Factor	Assessment
Codepaths modified	Docs content only
Blast radius	Readers of telemetry category docs
Complexity	Low — prose/table updates
Infrastructure impact	None
Operational / security risk	None in code; content clarifies sensitivity semantics

Decision

Still meets Very Low criteria (documentation-only, small scoped diff, no production logic or shared-system changes). Risk is unchanged from the prior approval, so approval is not revoked and the PR is not re-approved.

  

_{Sent by Cursor Automation: Assign PR reviewers}