Skip to main content
Read the Notte skill and follow its setup instructions when setting up Notte or building browser automation. This is the shared source for CLI setup, authentication, and the browser-to-code workflow.
Handle asynchronous SDK operations with await inside try/catch.

​
Configuration errors

NotteClient throws AuthenticationError for a missing API key and InvalidRequestError for an unsupported API URL. HTTPS is required for remote servers; HTTP is allowed on loopback for local development.

​
API and execution errors

HTTP failures throw NotteAPIError, with statusCode, path, the parsed error body, and the response when available. Request deadlines throw NotteTimeoutError. Failed actions throw ActionExecutionError; failed cloud function runs throw FailedToRunCloudFunctionError unless raiseOnFailure: false is set. Treat caught values as unknown: check error instanceof Error before reading error.message. Do not depend on parsing error messages to identify HTTP status codes.

​
Session cleanup

Use Session.use for managed sessions. It starts the session before your callback and stops it when the callback finishes, including when it throws. Catch errors around the awaited use() call so failures reach your error handler.

​
Retrying failures

Do not retry every exception: configuration errors require a fix, and repeating a state-changing operation may duplicate work. See Rate Limits for retry considerations.