Operational
These categories report on the session itself rather than page content.control answers “what did my agent do.” platform is mostly Kernel acting on the VM on your behalf - saving a profile, capturing a replay, polling a recorder - so it is off by default even though the rest of this group is on. Enable it when you are debugging a profile save, a replay, or a session-setup step rather than the agent itself.
control reports the commands a client sends over the CDP proxy that drive the browser - input gestures, navigation, dialogs, file selection, screenshots. It does not report configuration commands or the DOM and Runtime traffic that Playwright and Puppeteer issue on your behalf, and it collapses the phases that duplicate a gesture (mouseMoved, keyUp, char), so one action reads as one event.Browser activity
These categories report what’s happening in the page. Capturing any of them attaches a Chrome DevTools Protocol (CDP) collector to the session and produces highly granular page-level events. Capturing them adds overhead, so enable only the ones you need.interaction events are browser-native DOM events observed in the page, not calls to the computer-control API (those are reported by the control category).The monitor category
monitor reports the health of the CDP collector itself: monitor_disconnected, monitor_reconnected, monitor_reconnect_failed, and monitor_init_failed.
It isn’t directly settable. It flows automatically whenever any of the browser-activity categories are captured. You can still filter the stream by monitor to isolate these events.
Data sensitivity
Telemetry is off by default, and the default set carries session metadata with one exception:control records the source you submit for Playwright execution, because the code is the point of the event. The browser-activity categories are different again: they capture what actually flows through the session, which is your own browser’s data and can include credentials and personal information.
Captured events are persisted and can be replayed by resuming the stream, so this sensitivity applies to the data at rest, not just the live stream. Treat captured telemetry - and anywhere you forward or store it - with the same care as the underlying content. For how Kernel encrypts, retains, and processes data overall, see Security and the Data Processing Addendum.
Some exposure is reduced for you automatically: input into sensitive fields such as passwords is suppressed (
interaction_key isn’t emitted for them, and interaction_click omits the element text), and cdp_command reports how many characters a command submitted rather than the characters themselves (named keys such as Enter are reported, since a key name can’t be a typed character). Beyond that, because selection is opt-in, the most effective control is to capture only the categories you need - enable network, console, page, interaction, or screenshot deliberately, and prefer the operational categories when you only need session health.
If you capture control and run Playwright code, pass credentials in through variables your snippet reads rather than as literals in the submitted source, so the captured code doesn’t carry them.