Notte's own quickstart puts a stop sign in front of its SDK reference: automation written by hand breaks on dynamic selectors, auth state and anti-bot checks. The CLI exists so the element IDs in your script came from a real page load, and workflow-code turns that session into the script.
The Notte CLI, installed through the Homebrew tap or with go install. It starts remote browser sessions, observes real pages, handles login and session state, and exports the run as SDK code.
- Cloud browser sessions started and stopped from the terminal
- Notte page observe, which returns the element IDs on the live page so clicks target what is actually rendered
- Notte page click taking either an observed ID or a CSS or text selector
- Notte sessions workflow-code, which exports the session you just ran as code you can edit
- An interactive login that works in a non-interactive terminal, so auth completes in a browser instead of blocking on a key
- Functions: a tested browser task deployed so it can be invoked later as an HTTP endpoint, run from the CLI or SDK, or scheduled
Homebrew or Go to install, and one Notte login. The documented order is part of the tool: explore the live page first, export the code second, because element IDs and selectors written from memory fail on real pages.
One command plus a key — brew tap nottelabs/notte-cli https://github.com/nottelabs/notte-cli.git && brew install notte, then supply credentials