Browser extension (Chrome / Edge / Firefox)

❝ Someone else's webpage is still my debugging scene. ❞

The aiti-devtools browser extension (MV3): inject the in-page AI debugging assistant into any webpage — with zero changes to the target app (FAB 💬 AI + Inspector, element picking, AI window); together with the aiti-devtools bridge (local standalone bridge or pi-web), pi / claude / opencode agents can operate any page.

Capabilities

• Three browsers: Chrome / Edge (111+) / Firefox (128+, incl. full Firefox for Android ≥128 support); npm run build produces dist/{chrome,edge,firefox}, npm run package produces zips + the firefox .xpi
• Injection mechanism: a world:"MAIN" content script — the launcher source is inlined into content/main.js at build time and executed at file top level, unconstrained by page CSP; configuration lives in the isolated world (storage.sync → localStorage shared across worlds → read synchronously in the MAIN world at document_idle)
• Double-injection guard: the __dbgLauncherInstalled sentinel — pages that already run a launcher (like pi-web) are not injected twice
• options page (v2): AI target with three kinds (pi-web workbench / compatible agent host / cockpit fallback) + target address + one-click local pi-web probe (HEAD of the launcher asset on ports 30141/30142, auto-prefill; selecting pi-web also prefills the same-origin bridge address); site rules (default off + allowlist/deny regexes, deny wins); advanced (bridge address / AITI_BRIDGE_URL one-click copy); refresh the page after saving to take effect

Install

cd browser-ext && npm run build      # → dist/chrome dist/edge dist/firefox

• Chrome / Edge: chrome://extensions (or edge://extensions) → developer mode → load unpacked → dist/chrome (Edge: dist/edge)
• Firefox (temporary load): about:debugging#/runtime/this-firefox → load temporary add-on → dist/firefox/manifest.json (gone on restart)
• Firefox (permanent xpi): npm run package → dist/aiti-devtools-firefox.xpi — on ESR / DevEdition / Nightly set xpinstall.signatures.required=false and install from file for a permanent install; release / Android needs AMO signing (web-ext sign --channel=unlisted or upload as unlisted on AMO; stable gecko id aiti-devtools@aiti.ai is pinned; world:MAIN injection needs ≥128)

Usage

1. After installing, the FAB (💬 AI + Inspector) appears on any webpage
2. Click 💬 to open the AI window (default = the bridge's cockpit console)
3. Connect the agent side (pick one): pi (install aiti-devtools-pi, same bridge) / stdio shim (env AITI_BRIDGE_URL, one-click copy on the options page) / MCP ({ type:"http", url:"<bridgeUrl>/mcp/mcp" })

Prerequisite: the bridge is running (systemctl start aiti-bridge or node dev-repo/bridge/bin/aiti-bridge.mjs).

v2 enhancement (P0 shipped)

v1 defaulted to injecting on every page with the AI window pointed at the bare bridge + cockpit — misaligned with the motivation. v2 rebuilds this: (1) default off — popup "⚡ Enable on this page (once)" (runtime-only message, gone on navigation, wins over deny rules) + "★ Always enable this site" allowlist / deny regexes (deny wins); (2) the AI window defaults to pi-web (options-page one-click probe of local 30141/30142 with prefill; selecting pi-web also prefills the same-origin bridge address) / compatible agent host / cockpit fallback; (3) v1 settings migrate automatically (enabled→defaultEnabled, excludes→denySites, custom aiUrl→cockpitUrl), permission set unchanged (storage/activeTab/scripting/<all_urls>). P1/P2 (shortcut, connectivity self-check UI, per-site targets, strict-privacy mode) are finalized in the plan and rolling out.

Plan

Implemented 2026-09-16 (three-browser builds + end-to-end injection verification passed). Positioning: fills the "any webpage, no carrier" gap — project plugins only cover apps that adopt them, the pi-web extension only covers pi-web, port injection only covers proxied ports; the browser extension pushes coverage to all web pages.