Skip to content
K-Browser

Install

Requirements: macOS · Google Chrome 125 or later · Node.js 22 or later (node -v).

Below, k-browser means node src/cli.js run in the K-Browser folder. Run npm link once in that folder to have a k-browser command everywhere.

  1. Get the code

    Terminal window
    git clone https://github.com/kaiwutech-TW/k-browser.git K-Browser
    cd K-Browser
    npm install

  2. Register with your agents and start the bridge

    Run this in a real terminal, not through an agent:

    Terminal window
    k-browser install

    It asks which site categories to block for agents (comma-separated; Enter for none), creates a client with its own token for each agent and writes it into that agent’s MCP configuration, and installs the bridge as a LaunchAgent so it starts when you log in. Every file it changes is backed up first; k-browser restore <backup.json> puts one back.

    Without a terminal to ask in, give the answer on the command line, or install refuses:

    Terminal window
    k-browser install --block banking,email     # block these categories
    k-browser install --block ""                # block nothing

    --dry-run shows which files would change; --client claude-code|codex|antigravity|gemini-cli installs for one agent.

  3. Load the extension into Chrome

    Open chrome://extensions, turn on Developer mode, click Load unpacked and choose the extension/ folder (k-browser extension-path prints the full path). Pin the red K in the toolbar: you will use it when an agent hands a tab to you.

  4. Pair the extension with the bridge

    Terminal window
    k-browser pair

    Paste the code into the K-Browser popup and click Pair. The status turns green (Connected).

  5. Check

    Terminal window
    k-browser doctor

    "ok": true with startedBy: "launchd" means everything is ready. Restart your agent (or reconnect its k-browser MCP server) and it has the K-Browser tools.