We built the Notte Console so you could prototype, debug, and deploy browser automations in one environment.
Now you can control everything from your terminal.
What is Notte CLI?
Notte CLI brings full browser automation control to the command line. Start sessions, navigate pages, click elements, run AI agents, and scrape data; all without leaving your terminal.
Features
- AI agents - run and monitor AI-powered browser functions
- Browser sessions - headless or headed Chrome/Firefox with full control
- Files - upload and download files to notte.cc
- Output formats - human-readable text or JSON for scripting
- Personas - create and manage digital identities with email, phone, and SMS
- Secure credentials - system keyring for API keys, vaults for website passwords
- Web scraping - structured data extraction with custom schemas
- Functions - schedule and execute repeatable automation tasks
How it works
# Start a browser session
notte sessions start
# Navigate and interact
notte page goto "https://..."
notte page observe
→ B1, B2, I1...
notte page click B3
notte page scrape --instructions "..."
Need to see what's happening? notte sessions viewer opens the Console instantly.
Why it matters
Browser automations now fit into your existing workflows. Terminal + Console means you can build however you work best.
Get started
- Notte CLI: https://github.com/nottelabs/notte-cli
- Full documentation: https://docs.notte.cc/
- Watch Lucas, Nottelab's Founder & CTO, walk you through how to use it.
Top comments (2)
Bringing browser automation to the CLI is the right call for agent workflows — the browser is often the last thing still requiring a separate Python script.
One difference worth noting: browser-act (npx skills add browser-act/skills --skill browser-act) runs locally and can inherit your existing Chrome sessions (chrome mode), so the agent does not need to handle auth separately. The tradeoff is local vs Notte managed cloud sessions.
For Claude Code specifically, the CLI-as-skill model makes it composable: the model runs browser-act commands the same way it would any other tool.
the Personas feature is the part that caught my eye. managing digital identities (email, phone, sms) at the session level is one of those things that sounds simple but gets complicated fast once you're running anything at scale.
the hard part isn't creating the persona, it's keeping it consistent across sessions. browser fingerprint, timezone, language headers, webgl renderer - if any of those drift between sessions that were supposed to be the same "person", detection systems pick it up. have you thought about tying personas to a fixed fingerprint profile, or is that outside the scope of what notte is going for?
also curious about the credential vault - is it per-session or shared across personas?
Some comments may only be visible to logged-in visitors. Sign in to view all comments.