Skip to content

Document the platform category and correct control's sensitivity - #474

Draft
archandatta wants to merge 1 commit into
mainfrom
archand/kernel-1870/telemetry-control-platform-docs
Draft

Document the platform category and correct control's sensitivity#474
archandatta wants to merge 1 commit into
mainfrom
archand/kernel-1870/telemetry-control-platform-docs

Conversation

@archandatta

Copy link
Copy Markdown
Contributor

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.

@mintlify

mintlify Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

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

vercel Bot commented Aug 4, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
docs Error Error Aug 4, 2026 1:22pm

`control` used to be every in-VM API call, and the sensitivity table described
the whole default set as session metadata with no page content. Both are about
to stop being true: `control` narrows to actions that drive the browser and
gains the submitted Playwright source on `api_call`, VM-management calls move to
a new opt-in `platform` category, and browser-control commands sent over the CDP
proxy arrive as `cdp_command`.

The sensitivity table now calls out that a default-on category carries submitted
source, with the practical advice that follows from it: pass credentials through
variables rather than as literals in the snippet. Callers under a BAA get the
same note, since `control` stays available to them when the browser-activity
categories don't.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
@archandatta
archandatta force-pushed the archand/kernel-1870/telemetry-control-platform-docs branch from 21c25ec to 778a23a Compare August 4, 2026 13:22

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Risk assessment: Very Low

Verdict: Approve

Evidence (from diff)

  • 1 file changed: browsers/telemetry/categories.mdx (+15 / −5)
  • Documentation-only MDX update on a Mintlify docs site: 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; no prior approvals to re-evaluate

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

Meets Very Low criteria (documentation-only, small scoped diff, no production logic or shared-system changes). Approving.

Open in Web View Automation 

Sent by Cursor Automation: Assign PR reviewers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant