Skip to content

Downloads

Sparky coding at laptop

One command downloads the binary, stages the Chrome extension, and auto-configures all detected AI tools.

macOS / Linux:

Terminal window
curl -sSL https://raw.githubusercontent.com/brennhill/gasoline-agentic-browser-devtools-mcp/STABLE/scripts/install.sh | bash

Windows (PowerShell):

Terminal window
irm https://raw.githubusercontent.com/brennhill/gasoline-agentic-browser-devtools-mcp/STABLE/scripts/install.ps1 | iex

What this does:

  • Downloads the platform binary to ~/.gasoline/bin/
  • Verifies SHA-256 checksum
  • Extracts the Chrome extension to ~/GasolineAgenticDevtoolExtension/
  • Runs --install which auto-detects and configures: Claude Code, Claude Desktop, Cursor, Windsurf, VS Code, Gemini CLI, OpenCode, Antigravity, Zed

After running the installer, load the extension in Chrome:

  1. Open chrome://extensions/
  2. Enable Developer mode (toggle in top right)
  3. Click Load unpacked
  4. Select ~/GasolineAgenticDevtoolExtension

The extension captures browser telemetry and sends it to the local Gasoline server.

  • Annotation System Upgrade — Draw mode now pairs with review/export flows (annotations, annotation_report, annotation_issues) for multi-page feedback sessions.
  • Tracked Hover Island — A floating quick-action island on tracked tabs for one-click annotate, screenshot, terminal, and recording controls.
  • Built-In Terminal from the Page — Open the integrated terminal directly from the hover island and run live commands without leaving the browser.
  • Recording Approval UX — Clear pending/approved recording state in the popup, with explicit approve/deny flow and improved recording status feedback.
  • Context Menu Consistency — Dynamic start/stop labels for recording, annotations, and control states so extension actions always match runtime state.
  • Protocol & Reliability Hardening — Sync-path cleanup and stronger daemon/extension consistency for fewer tool-mode and state drift issues.
  • 5th Tool: analyze — Active analysis with 27 modes (DOM queries, accessibility, security audits, link health, visual annotations, API validation, forms, visual diff, and more)
  • Link Health & Validation — Browser-based link checker with CORS detection and SSRF-safe server-side validation
  • Draw Mode & Visual Annotations — Draw rectangles and type feedback directly on the page with multi-page sessions
  • Test Healing & Classification — Self-healing Playwright selectors and context-aware test generation
  • Recording & Playback — Full tab video recording with audio capture and log diff comparison
  • Terminal Integration — In-browser terminal with WebSocket relay and PTY session management
  • Multi-Client Support — Multiple AI tools can connect to the same daemon
Terminal window
git clone https://github.com/brennhill/gasoline-agentic-browser-devtools-mcp.git
cd gasoline-agentic-browser-devtools-mcp
make build
./dist/gasoline-agentic-browser-darwin-arm64 # or your platform binary

Available Binaries:

  • gasoline-agentic-browser-darwin-arm64 (macOS Apple Silicon)
  • gasoline-agentic-browser-darwin-x64 (macOS Intel)
  • gasoline-agentic-browser-linux-arm64 (Linux ARM64)
  • gasoline-agentic-browser-linux-x64 (Linux x86-64)
  • gasoline-agentic-browser-win32-x64.exe (Windows x86-64)
  • Browser: Chrome/Chromium 120+ (for MV3 support)
  • Runtime: Native Go binary (no Node.js required for standalone binary installs)
  • Node.js: 18+ (optional, only if you install via npm)
  • Platform: macOS, Linux, Windows
  • MCP Client: Claude Code, Cursor, Windsurf, Claude Desktop, Zed, Gemini CLI, OpenCode, Antigravity, or any other MCP-compliant system/agent

To verify the extension installed correctly:

  1. Open any webpage
  2. Click the Gasoline icon (Gasoline) in your toolbar
  3. You should see the popup with recording and tracking options
  4. Check the extension’s popup shows “Connected” status

To verify the binary:

Terminal window
~/.gasoline/bin/gasoline-agentic-browser --doctor

Extension not appearing?

  • Try refreshing the page (Cmd+R / Ctrl+R)
  • Ensure Chrome is version 120 or higher
  • Check that Developer mode is enabled

Recording not working?

  • Click the Gasoline icon and approve the recording request
  • Ensure the tab you want to record is the tracked tab
  • Check your Chrome permissions for microphone access (if recording audio)

Issues with MCP integration?

See GitHub Releases for complete version history.