Skip to content

Interceptor v2.1.12

Choose a tag to compare

@github-actions github-actions released this 11 Nov 14:18
· 14 commits to main since this release
95c7e93

Interceptor v2.1.12

What is Interceptor?

Interceptor is an AI-agent control surface for your browser, desktop apps, and iPhone. It works with your existing signed-in sessions through one CLI and local daemon.

  • Browser: read and act inside Chrome, Brave, Edge, and Safari, including page trees, network observation, rich editors, screenshots, and exports.
  • macOS: read and control native apps through Accessibility, trusted input, capture, and Apple frameworks. Routine work stays in the background.
  • Windows and Linux: use interceptor desktop with the native provider included in Full installs.
  • iOS: drive apps on an owned, unlocked, Developer Mode iPhone through the on-device XCTest runner, with separate device-service, Instruments, and WebKit lanes.

interceptor mcp install exposes these surfaces to supported MCP clients. No API key or separate automation browser is required.


What's new in v2.1.12

This release fixes two reported issues and clears every open dependency advisory on the repository. Thank you to @CupOfGeo and @Daheh for reports precise enough to reproduce on the first try.

Closing a group after several window new calls no longer crashes the browser (#336)

window new --group <label> moves your tab group into the new window. It used the browser's own group move for that. After the group had been moved twice, closing it crashed Brave and Chrome with a segfault, and group close timed out after 15 seconds. The crash reproduces in Brave (Chromium 156) and Chrome for Testing 157 with plain extension API calls, so it is a browser defect that this sequence reached every time.

Interceptor now moves the tabs themselves: it ungroups them, moves them to the new window, and groups them again under the same label, color, collapsed state, and order. Your group's auto-target carries over. The group's numeric id changes on each move; the label does not.

for u in https://example.com https://example.org https://example.net; do
  interceptor window new "$u" --group research
done
interceptor group close research     # closes 3 tabs, browser keeps running

One limit: a group that 2.1.11 or earlier already moved between windows, or that you dragged to another window by hand, still carries the browser state that crashes on close. No close order avoids it. Note the URLs, restart the browser, and reopen them in a fresh group. Updating the extension alone does not clear that state.

Windows: --trusted works, and capabilities tells the truth (#335)

On Windows, interceptor capabilities reported layers.os_input: true while act --trusted answered os_click not supported on Windows. A script could not pick a working input path from the reported capability.

Windows Full installs now deliver trusted click, key, and text input through the native provider. The page sees isTrusted: true. The tab has to be the active tab of the browser window that is in the foreground. A background window, a tab that is not showing, or a minimized window refuses before anything is sent, with a hint. Nothing is ever sent twice.

capabilities now reports each operation by itself under data.osInput:

"osInput": {
  "click": { "available": true, "foreground": true, "background": false,
             "reason": "Windows browser input is qualified only in the foreground; covered-window messages produced no page events" },
  "key":   { "available": true, "foreground": true, "background": false, "reason": "…" },
  "type":  { "available": true, "foreground": true, "background": false, "reason": "…" },
  "move":  { "available": false, "foreground": false, "background": false,
             "reason": "No safe pointer-path route in the native browser input provider" }
}

layers.os_input is true when click, key, and type are all available, which is what act, click, type, and keys --trusted need. A Windows Browser-only install reports all four unavailable and says the Full install is required.

Linux reports browser trusted input as unavailable in this release and refuses before delivery. The native route could not be proven to produce a trusted page event on the tested desktop, so it is not advertised. Synthetic input works as before. macOS behavior is unchanged; it now reports the same per-operation map.

A click that changes nothing says so, and one click stays one click

  • A synthetic click that causes no DOM change returns one warning with the exact next command: no DOM change after click; no trusted click was sent. If the site needs trusted events: interceptor click --trusted e12. Earlier results could claim an escalation to an OS click that was never delivered. Interceptor does not follow a synthetic click with a real one by itself, because that can press a submit or pay button twice.
  • scene click --os now sends its trusted click. Before, it reported one without sending it.
  • click --selector "<css>" --trusted used to drop --trusted without saying so. It now exits 1 before anything is sent and gives the two commands to run: interceptor query "<css>" for a ref, then interceptor click <ref> --trusted.

Dependency updates

rustls 0.23.46, swift-nio 2.100.0, swift-nio-extras 1.34.1, swift-nio-http2 1.44.0, Sparkle 2.9.2, the MCP SDK 1.32.0 with its updated dependency tree, and the DOM test packages. These close twelve dependency alerts and 47 bun audit findings. The patch that keeps large MCP stdio responses whole in the compiled CLI is carried forward to the new SDK.

One alert is dismissed instead of fixed: glib 0.18.5 ships in the Linux GTK overlay, and GTK 0.18 requires that line. Nothing in Interceptor or in the overlay's full dependency set for either Linux architecture calls the affected iterator, and a test now fails if product code starts to.

Behavior and compatibility

  • capabilities gains data.osInput. layers.os_input is now false on Linux and on Windows Browser-only installs, where it used to read true with no working route.
  • A new extension with an older daemon keeps working: macOS sends trusted input the way it did before, and Windows and Linux report trusted input unavailable until the CLI is updated.
  • The no-DOM-change warning text changed, and those results no longer carry an escalated field. Scripts that match the old wording should match the new one.
  • click --selector with --trusted or --os exits 1.
  • A group's numeric id changes when window new moves it. Address groups by label.
  • A command that targets a group in the middle of a move gets a retry message instead of acting on a half-moved group.
  • The CLI, daemon, Chromium MV3 and Electron MV2 extensions, macOS bridge, Safari app and extension, iOS runner, and Windows/Linux providers use version 2.1.12.

How it was tested

  • Release source: 2,606 tests passed, zero failures; TypeScript typecheck passed. The Chromium, Electron, and Safari background bundles build.
  • A signed, notarized Full 2.1.12 package was installed with the macOS installer and checked by hand on macOS 27:
    • #336: the reported sequence (three window new calls with 3 second waits, then group close) ran five times in a row in Brave and in Chrome for Testing. Every close removed exactly three tabs in under a second and the browser kept running. On 2.1.11 the same sequence crashed the browser every time.
    • Group regressions: one-window open and close, partial tab close, window close, the default group, a second agent's group left untouched, tab reuse and idle close, and new tabs landing in the group's own window. The browser's saved tab groups menu showed no leftover groups.
    • macOS trusted input to a covered window, a hidden tab, and a minimized window each delivered exactly one trusted click, with trusted Unicode text and Enter, and the frontmost app and cursor did not change.
  • Windows 11 ARM64 (build 26200), signed Full installer: the request from #335, act e1 --trusted --no-read --json --ws, produced one click with isTrusted: true; Unicode text and Enter were trusted; twelve requests against background, hidden, and minimized targets all refused with zero page events; with the provider missing, all four operations reported unavailable.
  • Linux ARM64 (Arch, Hyprland), Full archive: capabilities reports trusted input unavailable over both the local socket and --ws, and trusted requests refuse with zero page events.
  • On all three systems: the MCP stdio handshake and tool list, the destructive-action gates, and a 128 KiB response through the compiled CLI.
  • The macOS Browser, Full, and Safari packages were signed, notarized, and stapled. interceptor --version reports 2.1.12 (984df70) for the macOS, Linux, and Windows Full packages. The Windows Browser installers were built, signed, tested, and attested by the release workflow at the tag commit, which adds only a CI runner image pin on top of 984df70.
  • Not done here: the x64 Windows and Linux packages were built and signed but not installed on an x64 machine; Safari was not exercised live; Linux was not tried on X11.

Install

Existing Full users can run interceptor update. Package-loaded browser extensions can pick up the installed files with interceptor reload. The Chrome Web Store copy updates after the store finishes its review of 2.1.12.

Download Platform Includes
Interceptor-Browser-2.1.12.pkg macOS 11+, Apple silicon CLI, daemon, browser extension
Interceptor-Full-2.1.12.pkg macOS 15+, Apple silicon Browser package plus native macOS bridge
Interceptor-Safari-2.1.12.pkg macOS 14+ Safari app and Web Extension add-on
Interceptor-Browser-2.1.12-windows-x64.exe Windows 10 22H2+ x64 Per-user browser install
Interceptor-Full-2.1.12-windows-x64.exe Windows 10 22H2+ or Windows 11 24H2+ x64 Browser and native desktop provider with engines
Interceptor-Browser-2.1.12-windows-arm64.exe or Interceptor-Full-2.1.12-windows-arm64.exe Windows 11 24H2+ ARM64 Browser or Full install
Interceptor-Browser-2.1.12-linux-x64.tar.gz or linux-arm64.tar.gz Linux Browser archive
Interceptor-Full-2.1.12-linux-x64.tar.gz or linux-arm64.tar.gz Linux, glibc 2.39+ Browser and native desktop provider with engines

The macOS packages are Apple silicon only. Safari is a separate add-on. The version-free links at https://updates.hackervalley.media/latest/ point to the latest published packages.

SHA256SUMS-ALL lists the release files. Linux archives also have the CMS-signed SHA256SUMS, verified by verify-release-manifest.sh with the included pinned certificate. Windows installers use Authenticode signatures; Browser installers also carry GitHub build attestations.