experimental · v0.20.4

Your browser's AI,
inside your editor.

You're already signed in to ChatGPT. You already pay for it. AI Bridge attaches to that tab and drives it from VS Code — no API key, no second subscription, no new bill.

version 0.20.4 626 checks passing PolyForm Noncommercial 1.0.0 VS Code 1.90+ experimental
The AI Bridge chat panel with a streamed answer and a per-hunk proposal card
ChatGPT Claude Gemini your own
01

Built for the tab you already have open

A local bridge, your browser, your session. Nothing is proxied through anyone's server.

No API keys

Nothing to paste, nothing to leak, nothing to bill. The extension drives the page you're signed in to.

Your session, your model

The plan you already pay for, and the model you already picked — read straight from the page.

Edits you can refuse

Every change arrives as a proposal. Untick a hunk, accept the rest, one undo takes it all back.

Survives the usage limit

When ChatGPT says you've hit your cap, the context walks to Claude or Gemini by itself — boot prompt first, then only what changed. A badge on the reply tells you it switched.

37%
fewer tokens on repo context

Measured, not claimed. And the bigger lever: context is only attached when your question names a file, a symbol or a code term — a bundle costs 500–900 tokens.

500 MB browser cap

A 3-second watchdog evicts and collects at 80%, blocks at 100%. Low-end mode halves the boot and closes the local compressor.

Six settings tabs

Providers, router, compressor, state, repo, performance — every field, inline validation, and a live preview on each.

State that survives

Gzipped, encrypted, snapshotted. A ≤4k boot prompt restores what you were doing in a fresh chat.

02

It drives a tab, not an API

Three parts, all on your machine. The bridge never leaves loopback.

01 · EDITOR

VS Code extension

Panel, diffs, state, settings and commands — everything that touches your workspace. Ctrl+Alt+A opens the chat.

02 · LOOPBACK

Bridge process

A Node process on 127.0.0.1 with a token in ~/.ai-bridge/lock.json. Holds the adapters, the router and the watchdog.

03 · BROWSER

Your signed-in tab

Attached over CDP on port 9222. Never launched by the extension — only the window you opened.

03

What it does about tokens

Compression is noise on a terse prompt and a real 20–40% on verbose text. Measured with the project's own counter; identifiers, numbers, negations and code fences are checked to survive.

InputTokensSaved
Polite one-liner34 → 2138%
Terse one-liner8 → 80%
Verbose spec paragraph113 → 8029%
Pasted stack trace83 → 7114%
Code request68 → 5913%
Boot prompt975 → 9740%
Repo bundle588 → 37037%
04

What is proven, and what isn't

This is experimental software. The right-hand list matters more than the left.

Proven

  • 626 checks, 21 suites, on every push
  • Three adapters and a fourth custom one, end to end against fixtures
  • Per-hunk edits, locked-decision guard, drift refusal, one-undo applies
  • Boot under 4k with every delta present across five failovers
  • A deliberately broken fixture fails the suite — it detects breakage
  • The breakage report contains no chat content, checked against known fragments

Not proven

  • Live selectors — no adapter has run against the real sites
  • The one-hour memory soak — three minutes passes flat, an hour needs hardware
  • T1 / T2 quality — built and guarded, never run against a real model
  • Windows — the code exists, only Linux has been exercised
05

Install

Two commands, then attach the browser you're already signed in to.

terminal
# install the extension
$ code --install-extension ai-bridge-0.20.4.vsix

# open your browser with the debug port on (close it first)
$ chrome --remote-debugging-port=9222

# then, in VS Code
Ctrl+Shift+P  →  AI Bridge: Attach Browser
Ctrl+Shift+P  →  AI Bridge: Adapter Health   # green dot = working

If a dot is red, the site changed its page. Press AI Bridge: Export Breakage Report — it carries the host, the selectors tried and the tag/attribute names, and never a word of your conversation.