Migrate to Notte

Safely migrate browser automation from another provider to Notte with an AI coding agent.

AI agent instructions

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.

Use the Notte migration skills to move an existing browser-automation codebase to Notte with a visible plan, measured baseline, safe proof, tests, and a reversible rollout.

Install the skills

npx skills add nottelabs/notte-skills -y -g

The skills support migrations from Browserbase + Stagehand, Kernel, Anchor Browser, Browser Use Cloud, Steel, Hyperbrowser, and Skyvern.

Give this prompt to your AI coding agent

Copy the prompt below into Codex, Claude Code, Cursor, or another supported coding agent from the root of the repository you want to migrate.

Use $migrate-to-notte to assess and migrate this codebase to Notte.

Start by publishing a clear, user-visible phase plan. Complete the Notte
Quickstart before inspecting the repository. Detect the current browser
provider, inventory every workflow and dependency, measure the current cost and
latency where data is available, and run a safe read-only Notte proof.

Build the replacement progressively in an isolated area, add tests, run static
analysis and the full relevant test suite, and preserve public contracts. Keep
every change reversible. Do not touch production resources, credentials,
billing, or deploy to production without my explicit approval.

The skill routes the agent to the right provider-specific migration reference and keeps progress visible throughout the work.

Build a cost case first

Use the read-only cost-comparison companion when you want a migration business case before implementation:

Use $compare-to-notte-costs to scan this codebase and estimate the current
browser-automation provider's cost against an equivalent Notte workload.

Use current official pricing and my invoice or telemetry when available. Show
monthly and annual low/base/high scenarios, required concurrency, assumptions,
and excluded costs. Keep Browser Arena results separate as external benchmark
context; do not treat them as a forecast of this application's performance.

Skill source

• Migration skill
• Cost-comparison skill

Need help with a migration? Join the Notte community Slack.