Developer beta

A few steps.
A quieter browser.

Requires Node.js 22+, Chrome and an MCP-compatible AI client. The companion installs from npm. The extension is loaded by hand, because it is not on the Chrome Web Store yet.

  1. Connect your AI client. Pick the one you use.

    Codex

    npx lateef install codex

    Runs codex mcp add for you. If the codex command is not on your PATH, it edits ~/.codex/config.toml and keeps a copy of the previous file.

    Claude Code

    npx lateef install claude

    Runs claude mcp add --scope user, so Lateef is available in every project.

    Cursor

    npx lateef install cursor

    Adds a lateef entry to ~/.cursor/mcp.json, leaves your other servers alone, and keeps a copy of the previous file.

    Another client

    npx lateef config

    Prints the JSON for your client’s MCP settings. Add --toml if it wants TOML.

  2. Load the extension.
    npx lateef extension
    This copies the extension to ~/lateef-extension. In the Chrome profile you want, open chrome://extensions, turn on Developer mode, choose Load unpacked and select that folder. Keep the folder in place.
  3. Pair your chosen window.
    npx lateef pair
    Open Lateef’s popup in that existing Chrome window. Enter the displayed port and one-time code. Do not paste the code in chat or public issues.
  4. Check the connection.
    npx lateef doctor
    Start a new session in your client, then ask it to call browser_status and open a background test tab. Each session sees only its own tabs unless you share an existing tab.

First task to try

Open example.com in a new background tab.
Read its title and introductory text.
Close only the tab you created.

Read the source first

Everything npm installs is in the source download, with the tests. To run from source, extract it, run npm ci in that folder, and use node bin/lateef.mjs wherever the steps above say npx lateef.

Verify from the folder that holds the downloads: shasum -a 256 -c SHA256SUMS

Full control (optional)

The standard extension reads and acts on page elements and never uses Chrome’s debugger. A second version adds screenshots, real mouse and keyboard input, running JavaScript, and console and network logs. Use it for canvases and sites that ignore scripted clicks.

npx lateef extension --full

Load ~/lateef-extension-full at chrome://extensions in place of the standard one, pair it with npx lateef pair, and tick Full control in its popup. Chrome shows a “started debugging this browser” bar while it is in use. It gives an agent close to everything you could do in that tab, so switch it on only for clients and tasks you trust. Read the boundary.

Updating and uninstalling

To update, close your AI client, then run npx lateef@latest stop, npx lateef@latest install with your client’s name, and npx lateef@latest extension. Reload the extension in Chrome and start a new session. Local state lives in ~/.config/lateef; doctor reports mismatched versions.

To uninstall, remove the lateef entry from your client, run npx lateef stop, remove the Chrome extension, and delete ~/.config/lateef and ~/lateef-extension if you no longer want them.

Beta limits

Uploads: 1–4 authorized files, 25 MiB total, exact destination origin required. Attaching a file to a Gmail draft is checked on macOS. Passwords are unsupported. Canvas-only UIs and sites that need trusted input need the full control version. macOS is validated with an everyday Chrome profile, and Linux and Windows pass the automated tests. Understand what data is shared.