gaze

Most browser automation drives a fresh, anonymous browser. gaze drives the one you are already signed in to.

It is a CLI and a local stdio MCP server. It is not an AI agent: it has no model, no planning and no autonomy. An agent you run (Claude Code, Codex, any MCP client) drives gaze; gaze decides nothing.

• Reads never prompt. Anything that changes something asks first.

• Page content comes back wrapped and injection-scanned, never as instruction.

• Nothing listens on a network port, and nothing phones home.

Receipts

Related MCP server: YaviControl MCP Server

Install

git clone https://github.com/KevinTrinhDev/gaze && cd gaze && npm install
ln -s "$PWD/bin/gaze" ~/.local/bin/gaze     # Linux / macOS (Windows: WSL)

Quick start

gaze sync            # clone your logins (close that browser first)
gaze start           # open the automation browser (visible, on purpose)
gaze goto https://news.ycombinator.com
gaze map             # what is clickable, each with a reusable selector

Then read, click, fill, scrape, record, save sessions — see Usage. Anything that will not start: gaze doctor.

Drive it from an AI client

{ "mcpServers": { "gaze": {
    "command": "node", "args": ["/path/to/gaze/mcp.mjs"],
    "env": { "GAZE_APPROVAL": "fingerprint" } } } }

16 tools: read, map, click, fill, login (from a vault you unlocked), session, screenshot, challenge detection, batch. Stdio only, deliberately.

Guardrails

• Writes ask on the terminal, or for a fingerprint touch (GAZE_APPROVAL=fingerprint). No terminal, no opt-out → refused.

• grant approves once for a bounded window; there is no --forever.

• CAPTCHAs are detected and handed to a human — never solved.

• Passkeys and native sign-in stay human: gaze initiates, you complete.

• revoke stops everything. stats shows what ran. log shows what failed.

• It drives a browser holding your real sessions — treat it accordingly.

Browsers

Safari is unsupported (WebKit protocol, macOS only). One browser per identity: sync copies one profile. Roadmap: auto-discovery of whatever is installed — see Roadmap.

Docs

Use it with discretion: this drives a browser holding your live sessions and can act as you on any site you are signed in to. Many sites restrict automation; being logged in does not change that. Not affiliated with any browser vendor.

MPL-2.0 · part of the BASILISK ecosystem