Interceptor - Historical and Optional Material

Historical reference only. The interceptor and interceptor-daemon executables are not installed on this machine. Do not execute any interceptor command below. The material after this gate is retained only as historical and optional reference for a future explicitly installed Interceptor environment.

Current browser workflow: load the chrome-devtools-axi manifest skill and use /opt/homebrew/bin/chrome-devtools-axi. Follow its generation-prefixed ref contract, refresh snapshots after rerenders, and verify state changes with a fresh snapshot. If a requested capability exists only in the historical Interceptor material, fail closed and report that the optional runtime is unavailable. Do not redirect the user to stale setup paths automatically.

What It Does

Interceptor drives the real Chrome/Brave/Helium browser from inside it, and drives native macOS apps when the bridge is installed. Six capability classes, each its own verb tree: visual capture, DOM read, JS eval, network capture, input, and record/replay. It stays logged into your real sessions, passes every major bot-detection check, and is the mandatory tool for visual deploy verification.

The Problem

Headless browser tools speak CDP, which sites can fingerprint and block - so the automated browser sees a different page than a logged-in human does, or gets blocked outright. They also run as a separate browser instance with no auth, so they can't reach anything you're signed into. And when a page breaks - a blank screen after mount, a hydration mismatch, cards that flash and vanish - a screenshot tells you nothing about why. Interceptor solves all three: it operates through the actual browser UI (zero CDP fingerprint), uses your real signed-in sessions, and reads the live DOM, console errors, and network traffic to explain failures a screenshot can't.

How It Works

Interceptor is a Chrome extension that operates through the actual browser UI plus an optional macOS bridge that extends the same control surface to native apps, OS-level input, and on-device VMs.