FastLink
Driving a real Chrome tab

When the page breaks, the automation doesn't.

FastLink is a resilient browser-automation layer that bridges an AI agent to a real Chrome tab — and keeps working when the page fights back.

It reads and drives pages through the DOM by default — fast and precise. When the DOM can't see a target (a cross-origin iframe, canvas, or image-only UI), it falls back to a vision tier that looks at the screenshot and returns coordinates. Add automatic retries and read-back verification, and a flaky page stops being a dead end.

// the fallback path

DOM
Read & act on the structure
fast_snapshot indexes the live DOM; fast_click / fast_fill_form act on it. The fast, exact path — tried first, every time.
Vision
Look at the pixels instead
When the snapshot comes back empty (opaque iframe, canvas, custom UI), the vision tier reads the screenshot and returns coordinates for fast_point / fast_fill_vision.
Verify
Confirm it actually landed
A fresh capture reads back the field before reporting success — no false positives where the click missed but the tool claimed it worked.

// why it holds up

Built for the pages that don't cooperate.

Real automation runs into loading spinners, rate limits, and UIs the browser can't introspect. FastLink treats those as the normal case, not the exception.

DOM-first speed

Structured snapshots and precise clicks are the default — the cheapest, most reliable way to read and drive a normal HTML page.

Vision fallback

Cross-origin iframes and canvas UIs are invisible to the DOM. The vision tier reads the screenshot and hands back pixel coordinates so the action still lands.

Retries with backoff

A transient 503 from the vision service is auto-retried with backoff inside the tool, instead of surfacing as a hard failure the agent has to recover from.

Read-back verification

Before reporting a fill as done, a fresh capture confirms the value actually landed — killing the false positives where a mistargeted click silently typed nothing.

Batched sequences

Chain a known path — navigate, fill, click, wait — into a single call. Fewer round-trips, less latency between the steps that matter.

Your real browser

It drives the actual Chrome tab you're logged into — through a WebSocket broker that lets several agent sessions share one browser, locally or via a cloud relay.

// how it connects

A thin bridge, end to end.

AI agent MCP server broker (WebSocket) Chrome extension the page
The broker multiplexes every connected session onto one extension socket, so multiple agents can drive the same tab. Runs locally next to Claude Code, or through a Cloudflare relay for browser control from the web.
⌂ DashboardDesign ·ClaudeCodexGrokGeminiDeepSeek