Skip to main content

The Notte Blog

A lit reading room opening through tall windows onto a dark harbour
Integration

Claude Managed Agents x Notte: What the Sandbox Can't Reach

Claude Managed Agents gives an agent a sandbox, a credential vault, and a schedule. It does not give it a browser. Here is why the web outside the sandbox is a structurally different problem, how the vault hands over a key without handing over the key, and what a Notte persona can finish that a browser alone cannot.

Andrea's avatarAndrea
Browser harnesses compared: notte-cli, agent-browser, browser-harness, playwright-mcp
Engineering

Browser harnesses compared: notte-cli, agent-browser, browser-harness, playwright-mcp

An objective walkthrough of browser harnesses for AI agents in 2026: Vercel's agent-browser, Browser Use's browser-harness, Microsoft's playwright-mcp, and Notte's notte-cli. What each one is, how they differ, and how to pick.

Leo's avatarLeo
The browser automation stack in 2026: which tool for which job
Engineering

The browser automation stack in 2026: which tool for which job

A category-by-category map of the AI browser agent landscape: the agent libraries, the cloud browsers, the web data layers, the consumer products, and the full-stack platform that ties them together.

Leo's avatarLeo
Web Automation in 2025: API-First vs Browser Automation (And Why You Need Both)
Engineering

Web Automation in 2025: API-First vs Browser Automation (And Why You Need Both)

APIs are fast but limited in scope. Browsers are universal but fragile. The winning approach in 2025 is hybrid: API-first where possible, agent-driven browser automation where necessary.

Sam's avatarSam
History of Browser Automation Framework: From Scripts to Agents
Engineering

History of Browser Automation Framework: From Scripts to Agents

From Selenium in 2004 to LLM-powered agents today — how each wave of browser automation solved one bottleneck and exposed the next.

Sam's avatarSam
x402 and Notte: Building Blocks for Autonomous Agent Infrastructure
Engineering

x402 and Notte: Building Blocks for Autonomous Agent Infrastructure

The dormant HTTP 402 status code is now enabling autonomous agents to pay for web resources via blockchain micropayments. How x402 completes the vision of truly autonomous web agents.

Sam's avatarSam
Next
The Notte Blog