v0.11.0: Chrome Web Store support, extension 0.10.0

What's new since v0.10.1

• Chrome Web Store support (#16). The relay accepts the store copy of the extension beside your own unpacked copy, applies store updates once no agent tab is open, and doctor shows which copy each profile runs. The store listing is in review. Until Google publishes it, setup and doctor keep installing from your clone (Load unpacked) and call the store version coming soon.
• Extension 0.10.0. No new permissions. A second copy of the extension in the same profile is refused with a clear message.
• The README explains chrome-relay do up front: one command for a whole goal, the live speeds with Jev (a 7-step form in 2.5 s, 1.2 s replayed), how a step is decided and when it hands back, and how the decision models compare. See also the approach.

Permission model

The relay accepts one more extension: the official Chrome Web Store copy, identified by its store ID, in addition to your own unpacked copy. As before, only from the Chrome process. Load your clone's copy instead if you'd rather trust only code you pulled.

Status

• The Chrome Web Store extension and the iPhone app are in review: coming soon. Until then, build from source.
• Signing in with a password manager works with 1Password only for now.

Update

cd <your clone> && git pull && ./build && chrome-relay update

v0.10.1: the website matches how it works today; iPhone app 1.0 in review

What's new since v0.10.0

• The website is rewritten to match how Chrome Relay works today: whole goals with chrome-relay do, signing in with 1Password, saving new logins, Secure Enclave passkeys, and approving on your Mac or a paired iPhone. https://agent-chrome-relay.aindeev.com (#23)
• Latest speeds with Jev, measured in a real Chrome: a 7-step form in 2.5 s, 1.2 s replayed from a saved flow, a Wikipedia search through its suggestions in 2.0 s. Click by click, an agent needs about 20 s for the same form. Details: the approach.
• iPhone app 1.0: Chrome Relay Approve is iPhone only, has a privacy policy for its App Store listing, and declares its encryption as exempt (#21, #22).

Status

• The Chrome extension is in Chrome Web Store review and the iPhone app is in App Store review: both are coming soon. Until then, build from source: load the extension from your clone and build the iPhone app with Xcode (./ios/build).
• Signing in with a password manager works with 1Password only for now.

Update

cd <your clone> && git pull && ./build && chrome-relay update

v0.10.0: agents carry out a whole goal in one command

The first tagged release of Chrome Relay. Headline: chrome-relay do.

chrome-relay do

Driving a page one agent-browser command at a time costs the agent a model round trip per click: the relay answers in ~15 ms, the agent thinks for seconds. Now the agent states the goal once:

agent-browser --cdp "$(chrome-relay url you@company.com)" open https://app.example.com/team/invite
chrome-relay do "Invite the new teammate as an admin" \
  --data "Email=ada@example.com" --data "Role=Admin" --until "text:Invitation sent"

• Saved flows: a run that ends with --until met replays on that site without a model, with new data.
• The agent's data fills the fields it names, with no model; op:// references are typed from 1Password as before.
• A fast decision model for the rest: TypeSafe's Jev (~0.15 s a step, pbpaste | chrome-relay decider jev), else Claude Haiku through your own Claude Code (~1–1.5 s).
• Checked steps: before each action, the element is still the one decided on, enabled, on screen and not covered; after, the page settles and the change is read back.
• Hands back what it isn't sure of (exit code 2): low confidence, missing values, unrequested delete/send/pay/deploy/authorize clicks, covered buttons, loops, leaving the site. "Done" needs --until.
• chrome-relay decider, chrome-relay flows, status in doctor; the skill teaches agents to use it.

In a real Chrome with Jev: a 7-step order form in 2.5 s, the same form replayed in 1.2 s, a Wikipedia search through its suggestions in 2.0 s.

Why it's built this way, and how Jev, Haiku, Cloudflare's Clef, Gemini and local models compared: the approach.

Also in this release

• The iPhone approver: a push relay wakes the iPhone app, so Macs don't need the APNs key (#17); the relay carries the messages too, so the Mac and the iPhone meet in one place (#19); ios/release sends the app to TestFlight (#13).
• Agents save the logins and 2-step codes they create, through 1Password (#12).
• A privacy page for the Chrome extension (#18).
• A link inside a search suggestion counts as one choice, not two (#15).

Update

cd <your clone> && git pull && ./build && chrome-relay update
chrome-relay doctor      # the last line says which decider `chrome-relay do` uses

New install: see the README.