Hanzi Browse

The context layer for browsing agents.

Your browsing agent keeps failing on real sites. Hanzi Browse ships 24 site playbooks — hints for the LLM, not brittle scripts — so it actually finishes the task.

Hanzi Browse demo video thumbnail
For your agent — works with Cursor Claude Code Gemini CLI Codex CLI VS Code Copilot Antigravity Kiro OpenCode Pi
Already knows how to use X LinkedIn Gmail GitHub Notion Figma Slack Reddit Amazon Zillow Indeed Google Docs + 12 more
For your agent

A browser sub-agent for your coding agent.

One command installs it. Your agent delegates browser work — clicking, reading, filling forms in your real signed-in Chrome — and keeps its context free for code.

  • One command setup. Detects every agent on your machine and wires Hanzi Browse into each one's MCP config.
  • Ships with a site-knowledge layer. 24 verified playbooks (X, LinkedIn, Gmail, Notion, Zillow…) auto-loaded by URL — the context big-tech agents don't have.
  • Offloads the browser, not your context. The sub-agent runs the loop — read page → plan next action → click/type/scroll → observe → repeat until done — then returns a clean answer. Your main agent fires one tool call and gets the result.
Install — it's free
For your product

Browser automation for your users, described in English.

Your backend sends a natural-language task. Your users' own Chrome runs it. Same engine, same site knowledge as the CLI — packaged as a REST API and @hanzi-browse/sdk.

  • Describe, don't script. runTask({ task: "…" }) — no selectors, no Playwright.
  • Your users stay in control. They pair their own browser; you never touch credentials.
  • Same infra as the CLI. Free tools on tools.hanzilla.co are SDK demos.
Get an API key
For your agent

A browser sub-agent for your coding agent.

One command installs it. Your agent delegates browser work — clicking, reading, filling forms in your real signed-in Chrome — and keeps its context free for code.

INSTALL HANZI
npx hanzi-browse setup
1 Installs the Chrome extension
2 Configures MCP server + browser skills
3 Choose: we handle the AI, or bring your own key
Managed We handle the AI. 20 free tasks/month, then $0.05/task.
Bring your own model Use your Claude Pro, GPT Plus subscription, or any API key. Free forever, runs locally.

What you can do with it

Setup ships open-source skills for common workflows. Your agent picks the right one for the task — or you can mention the skill by name.

Browse all skills on GitHub →

For your product

Browser automation for your users, described in English.

Your backend sends a natural-language task; your users' own Chrome runs it. Same engine, same site knowledge as the CLI — packaged as a REST API and @hanzi-browse/sdk.

How it works

1 and create an API key
2 Send your user a pairing link — they click it and connect
3 Run tasks from your backend, show results in your app

Need volume pricing? Talk to us.

Quick example

import { HanziClient } from '@hanzi-browse/sdk';

const client = new HanziClient({
  apiKey: process.env.HANZI_API_KEY,
});

// Pair a browser — give the URL to your user
const { pairingToken } = await client.createPairingToken();
// User visits: https://api.hanzilla.co/pair/{pairingToken}

// Find their connected session
const sessions = await client.listSessions();
const browser = sessions.find(s => s.status === 'connected');

// Run a task
const result = await client.runTask({
  browserSessionId: browser.id,
  task: 'Read the patient chart on this page',
});

console.log(result.answer);
Free tools — built on the SDK

See it in action — no install.

Hosted apps built on the SDK you just read about. Paste a URL, pair your browser, watch it run.

Pricing

Free to start. Pay per task.

Only charged for completed tasks. Errors and timeouts are always free.

Managed

$0.05 / task

20 free tasks/month included

  • We handle the AI — no API key needed
  • Only charged for completed tasks
  • Errors and timeouts are free
  • REST API + MCP + TypeScript SDK
BYOM

Free

You provide your own AI model

  • Use your Claude, GPT, or Gemini key
  • Everything runs locally
  • No data leaves your machine
  • Unlimited tasks
FAQ

Questions people actually ask.

Short answers. Open any to expand.

How is Hanzi Browse different from Playwright, Puppeteer, or Browserbase?
Those spin up a fresh, clean browser in a sandbox — you re-login, fight CAPTCHAs, maintain cookies. Hanzi Browse attaches to your existing Chrome via the DevTools Protocol, so sites see the session you're already logged into: Gmail, LinkedIn, your bank, your company's admin tools. No login automation, no session replay, no detection arms race.
Do I need a new API key, or can I reuse my Claude Pro / ChatGPT Plus subscription?
Reuse what you already pay for. In BYOM mode, Hanzi Browse reads credentials from Claude Code's OAuth, Codex's auth.json, the macOS Keychain, or a plain API key — whichever you have. If you already pay for Claude Pro/Max or GPT Plus, it's effectively free. No extra billing.
Does my browsing data go to Hanzi Browse's servers?
Depends on the mode. BYOM: nothing touches Hanzi Browse servers — screenshots go directly from your machine to the AI provider you picked. Managed: pages and screenshots are processed by Google Vertex AI (Gemini) and not retained beyond the task. Hanzi Browse never tracks browsing outside active tasks and doesn't sell data.
Can I embed Hanzi Browse in my own product?
Yes. There's a REST API and a TypeScript SDK (@hanzi-browse/sdk). Your user pairs their browser once via a pairing link, then your backend calls client.runTask(...) against their session. Billing is $0.05 per completed task — errors and timeouts are always free.
Start here

One command. Real browser.

Or read the developer guide to embed Hanzi Browse in your product.

npx hanzi-browse setup