kinbrowserdocs

The Kin Browser guide

Three parts, in the order people need them:

  • First steps: your first ten minutes.
  • Everyday use: what you will do every week.
  • Advanced: for teams, QA and the built-in agent.

Each part says which edition it needs. Lite is free.


1. First steps (10 minutes, Lite)

What Kin Browser is. A browser you and your AI agents share. You browse in your tabs; your agents work in theirs, gathered in named spaces you can watch, pause or take over. Agents never see your own tabs.

1. Install and open it. Download it from kinbrowser.com, install, and open Kin Browser. Its window opens with the Grid: every space, what needs you, and the Settings link at the top.

2. Connect your AI agent. Kin Browser works with Claude Code, Codex, Cursor, Claude Desktop or any MCP client.

  • Claude Code: in Settings → Use with Claude Code, press Connect Claude Code (or run kin-browser skill install). It adds Kin Browser's skill and tools to your Claude Code, which runs on your own Claude plan or key; Kin Browser never sees that sign-in. Then ask Claude to "use kin-browser".
  • An MCP client: add the server kin-browser mcp (stdio).

3. Give your agent a first job. For example: "Use kin-browser to compare the 14-inch MacBook Pro on three Malaysian shops, with sources." Watch its space appear in the Grid. Each step shows what it did and why.

4. Answer when it asks. A CAPTCHA, a sign-in, a code or a choice only you can make: the agent asks, and the Grid shows the question at the top. Answer there, or press Done after doing it yourself in the agent's tab.

5. Keep control.

  • Under Settings → Task limits: the steps, minutes and sites a task may use before it stops and asks you.
  • In the Grid: Ask before new websites and Ask before risky actions (paying, deleting, sending, submitting).

6. Sign-ins without passwords. Save a sign-in in the Vault. Agents use it with sign-in, and never see the password.

That is all you need for most work. Everything below is when you want more.


2. Everyday use

Recipes (Lite). A task that worked can be saved, and run again by name with new values: save-recipe, recipe check-invoice invoice_no=…. Turn on recording in the Grid to make one.

Watches (Lite). Tell me when a page changes, or when a price drops: watch <url> --text "In stock" --every 15.

Site notes (Lite). What the next agent should know about a site ("prices exclude SST"). Agents read them when they open the site. Edit them in Settings → Site notes.

Data out of pages (Lite).

  • extract: tables and repeated cards, as rows.
  • network: the JSON the page fetched.
  • read-document: a PDF or a spreadsheet the agent downloaded.

Batches (Lite). One action over many rows (a spreadsheet of accounts). Use --approve each for anything that submits.

Developer checks (Lite).

  • expect, logs, request;
  • saved sign-in states (save-state, load-state);
  • test data (fake-data), a test inbox and traces.

Testing what you build on this computer (Lite). Open Settings → Local browsing and choose Ask me each time. When an agent opens localhost:3000 or another local address, the Grid asks you: Allow once, Always, or Decline. Take any back in Settings.

Files on this computer (Lite). Agents can read your files and save reports, one folder at a time: the first time, the Grid asks you (Allow once, Always, Decline), and saving is asked separately from reading. Manage them in Settings → Files & folders. See local-files.md.

QA and QC (Pro).

  • kin.yaml tests and CI (kin-browser test, kin-browser ci);
  • visual diffs, screen sizes, crawls, accessibility, performance;
  • comparisons, mocks and bug reports;
  • tests written by AI;
  • website QA: SEO, rankings, landing-page checks.

See testing.md.

Upgrading. Type a licence key in Settings → Licence & version. Kin Browser upgrades itself: there is no other download. Lite can try Pro free, and Pro can try Premium free, from the same place.


3. Advanced

Teams and companies (Premium).

  • People, roles and single sign-on (teams.md).
  • Approvals from Slack, Teams, WhatsApp and phones (chrome-and-phones.md).
  • Automations with Google Workspace and Microsoft 365, and plugins (automations.md).
  • Sales, marketing, CRM and support tools (revenue.md).
  • Fleets of machines, policy as code with DLP and compliance recording, SIEM, data residency, your own KMS key, SCIM, your own update channel (enterprise.md).

Kin Browser as the agent (Ultra). No other agent needed:

  1. In Settings → Model accounts, connect your ChatGPT plan (Codex) or a Claude API key.
  2. Type what you want in the Grid's Ask Kin box, or run kin-browser agent "…".

It plans, browses and finishes by itself, within your limits. Ask about the tab in front of you from the side panel; follow up on an answer; say "every Monday at 9…" for a routine; ask for a spreadsheet, a document or slides; or message it from Telegram (Settings → Phone & cloud). When it finishes, Save as PDF or Save as Markdown puts the whole task in your Downloads. It can also schedule goals, remember sites, hand you bot checks, learn a task you show it once, and write research (meeting prep, the weekly brief). See built-in-agent.md and tasks.md.

Early versions. An invitation key (typed where licence keys go) puts this computer on beta or alpha builds. Settings → Updates → Back to the stable release returns it in one click.

From scripts and other tools.

  • every command: kin-browser help, or commands.md;
  • every MCP tool: mcp-tools.md;
  • the HTTP API and remote MCP of a cloud machine: chrome-and-phones.md;
  • Zapier, Make and n8n: integrations.

When something is wrong.

  • kin-browser status: is it running, and where.
  • kin-browser logs: a page's errors.
  • kin-browser licence: the edition, the licence and the version.
  • Settings → Report a problem: sends it to us with your version and system, never your pages.