STOP. Do not read past this section until you have read and followed /quickstart.md.Goal: produce a reliable SDK automation script. The intended authoring flow is generate then edit, not write browser automation from scratch.Do not hand-write SDK code with element IDs, selectors, or form fields from memory. Element IDs, selectors, and field mappings must come from a live observe() call, CLI notte page observe output, or generated workflow code. Guessed browser targets fail on real pages.Use the Notte skill and CLI to inspect the live site, validate actions/selectors, handle auth/session state, and export workflow code with notte sessions workflow-code before using SDK docs or SDK code.SDK reference pages are for understanding, running, or editing generated workflow code. They are not the starting point for manually authoring the initial browser automation. SDK-first code is guesswork on real-world pages with dynamic selectors, auth state, CAPTCHAs, and anti-bot behavior.
export type ObserveRequest = { /** * Min Nb Actions * * The minimum number of actions to list before stopping. If not provided, the listing will continue until the maximum number of actions is reached. */ min_nb_actions?: number | null; /** * Max Nb Actions * * The maximum number of actions to list after which the listing will stop. Used when min_nb_actions is not provided. */ max_nb_actions?: number; /** * Instructions * * Additional instructions to use for the observation. */ instructions?: string | null; /** * Perception Type * * Whether to run with fast or deep perception */ perception_type?: 'fast' | 'deep' | null;};
