📄️ Get Started
Autopilot is the session-recording SDK that powers session replay. It records what happens on a page — the initial DOM, every subsequent mutation, and user interactions such as scrolling, resizing, and pointer movement — then binary-encodes, compresses, and uploads that stream so a session can be replayed later.
📄️ Initialization & Enablement
Autopilot is never initialized directly by your application. It is loaded by the Pulse SDK during Pulse's own startup, and only when two independent gates are both satisfied. This page explains the full flow and how to control whether recording happens.
📄️ Masking Sensitive Inputs
Session recordings capture the live DOM, which can include values typed into form fields. To keep sensitive data out of recordings, Autopilot masks the values of certain input fields before they are encoded and uploaded. Masking happens on the recording side — the original value never leaves the page.
📄️ Mask State API
Masking keeps sensitive values out of Autopilot recordings — see Masking Sensitive Inputs. But a host application often needs the same information for its own purposes: a native webview shell that captures screenshots, for instance, has to know where the masked elements are on screen so it can obscure those regions in the image it captures.