Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.notte.cc/llms.txt

Use this file to discover all available pages before exploring further.

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.
OpenClaw is an open-source personal AI assistant you run on your own devices. Its browser tool can drive any Chrome DevTools Protocol (CDP) endpoint — by pointing it at a Notte session URL, every browser task OpenClaw runs executes on a Notte cloud browser with built-in stealth, residential proxies, and anti-detection.

​
Prerequisites

​
Connect OpenClaw to a Notte browser

OpenClaw’s browser tool supports remote CDP profiles. Add a notte profile to ~/.openclaw/openclaw.json: 
{
  "browser": {
    "enabled": true,
    "defaultProfile": "notte",
    "remoteCdpTimeoutMs": 3000,
    "remoteCdpHandshakeTimeoutMs": 5000,
    "profiles": {
      "notte": {
        "cdpUrl": "wss://us-prod.notte.cc/sessions/connect?token=<NOTTE_API_KEY>",
        "color": "#7C3AED"
      }
    }
  }
}
Replace <NOTTE_API_KEY> with your key from the Notte console. That’s it — OpenClaw now runs its browser tool on a Notte cloud browser.
The wss://us-prod.notte.cc/sessions/connect endpoint creates a fresh browser session when OpenClaw connects and tears it down when the connection closes — there is no manual session lifecycle to manage.

​
Run a browser task

Start the profile and drive it from the OpenClaw CLI: 
# Start the Notte-backed browser profile
openclaw browser --browser-profile notte start

# Open a page
openclaw browser --browser-profile notte open https://example.com

# Capture a screenshot
openclaw browser --browser-profile notte screenshot
Once the profile is running, OpenClaw’s agent uses it automatically for any task that needs a browser — every page load, click, and screenshot executes on the Notte cloud browser.

​
Benefits of using Notte with OpenClaw

  • No local browser management: run OpenClaw’s browser tool without installing or maintaining Chrome locally
  • Stealth & anti-detection: built-in fingerprint hardening and CAPTCHA solving
  • Residential proxies: route traffic through residential IPs across regions
  • Live session view: watch any running session from the Notte console
  • Scalability: each connection gets its own isolated cloud browser, so multiple OpenClaw instances run in parallel without contention