Skip to main content
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.
Source: node-sdk/src/lib/client/types.gen.ts

Fields

string
required
The task that the agent should perform
string | null | undefined
The URL that the agent should start on (optional)
unknown
The response format to use for the agent answer. Use a JSON Schema object; high-level Node agent and scrape methods also accept a Zod schema
number | null | undefined
[Experimental] The step from which the agent should gather information from in the session. If none, fresh memory
string | undefined
The reasoning model to use
boolean | undefined
Whether to use vision for the agent. Not all reasoning models support vision.
number | undefined
The maximum number of steps the agent should take
string | null | undefined
The vault to use for the agent
string | null | undefined
The persona to use for the agent
{ [key: string]: unknown; } | null | undefined
Config used for the notifier
string
required
The ID of the session to run the agent on