pastilhasandClaude Opus 5
c0e0848e6a
Two halves of the same coupling, both left behind by this morning's extraction. The pairing UI was Settings/IntegrationsSettings/BrowserRelay.tsx — a PLATFORM screen driving this plugin's pairing, calling /browser/relay-token, and working only because the plugin happens to serve that path. It is a panel here now, beside the tab list rather than buried in settings: it shows whether the extension is connected and how many tabs it holds, which is the first thing anyone looks at when a capture does not work, and that is not configuration you set once. The download link pointed at public/browser-relay-extension.zip, a static file. That file was 58 lines behind the source it claimed to be — built in August from something that predated a February commit, never rebuilt, and serving an extension missing the multi-session recovery path that the same February commit added. Anyone downloading it got the version that cannot recover from exactly the failure they were about to hit. So the archive is built from the extension directory per request. There is no second copy to fall behind, which is the only durable fix for that class. zip.ts is hand-rolled and stored rather than deflated. The route's own history says it used to shell out to `zip`; this manifest's "nothing to declare" is worth more than 30 KB on a download that happens once, and Chrome accepts stored entries. Timestamps are fixed at the format's zero so the same directory always produces identical bytes — which is what makes the ETag meaningful and "did this change" answerable by comparing two files. Verified by unzipping the output and diffing background.js against the source. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Browser
Drive your own browser from Officer — your tabs, your sessions, your logins.
This is not a scraper. It attaches to the Chrome you are already using, so a page behind a login is a page Officer can see, because you are signed in to it. Ask an agent about what is on your screen, have it read a tab, navigate, or take a screenshot of something no headless browser could reach.
You install an extension. The plugin ships it; Chrome loads it from disk, and you paste one address and
one token from Settings to pair. extension/SETUP.md has the steps.
Each account pairs its own browser. Two people on one server drive two different browsers, and neither can see the other's tabs.
Not yet tested end to end. The relay moved from inside the platform to its own process as part of this
extraction, and no browser has been paired against it since. It typechecks and installs; whether an
extension connects is the next thing to find out. BLOCKERS.md is honest about the rest.
Needs no host packages — the relay is Bun, and Chrome is on whatever machine you are sitting at.