zpwrchrome // recent tabs

features

keyboard commands

Chrome caps default-suggested shortcuts at 4. The remaining 51 commands are bound by the user in chrome://extensions/shortcuts.

popup categories

The toolbar popup (popup.html / popup.css / popup.js) renders 12 categories, each fzf-scored against tab title + host. Jump straight to a category with Cmd+1..Cmd+0 (the digit shown beside each row); Cmd+P and Cmd+K jump to the Pass and Tech categories. Type to fuzzy-filter, ↑/↓ to move, Enter to activate, Del to close/forget the highlighted row.

how it works

zpwrchrome is a Manifest V3 extension. The service worker (background.js) tracks tab activation across every window in chrome.storage.session so the MRU stack survives service-worker restarts, dispatches the 55 keyboard commands, answers the 19 message kinds the popup / modal / managers send, registers userscripts, and bridges to the native host for pass and segmented downloads.

On-page features ship as content scripts rather than DevTools panels: a page-theme injector (modal/cyber-theme.js) paints arbitrary pages with the HUD palette at document_start; reader mode (modal/reader-mode.js) extracts the main article into a sanitized overlay; Turn Off the Lights (modal/lights-off.js) dims the page while lifting <video> elements above the overlay; a JSON viewer (modal/json-viewer.js) and XML viewer (modal/xml-viewer.js) replace raw structured-data pages with collapsible trees (RFC 6901 pointer / XPath copy). The find-in-all-tabs page scrapes innerText from every open http(s) tab in parallel (capped at 200 KB / tab) and fuzzy-filters across them, scrolling the chosen tab to the match via window.find().

Pure helpers live in lib/util.js and lib/fzf.js with zero chrome.* references, so they unit-test headless in plain Node and can be inlined into the shadow-DOM modal by scripts/build-modal.mjs. The fzf scorer matches the constants used across the MenkeTechnologies tools (boundary 9, camel 7, gap-start −3, match 16).

native host (zpwrchrome-host)

pass, GPG, and segmented downloads can't run inside an MV3 service worker, so a small Rust binary handles them over Chrome native messaging (length-prefixed JSON on stdio). It is a strict 1:1 port of browserpass-native v3.1.2 with six additive Rust tool families layered on top — matched before the ported upstream switch, so a stock browserpass client still gets byte-identical upstream behavior. Install and register it for your extension ID:

1. cargo install zpwrchrome-host
2. zpwrchrome-host --install <ext-id> — writes the native-messaging manifest (host name com.menketechnologies.zpwrchrome) into every detected Chromium-family browser config dir on macOS/Linux. Find the ext-id at chrome://extensions (Developer mode).
3. zpwrchrome-host --version / -V — print version and exit. -v logs verbosely to stderr. --help / -h prints usage.

With no flags the host reads one framed JSON request on stdin, dispatches it, and exits — one process per request, mirroring upstream. It handles the upstream browserpass actions configure, list, tree, fetch, save, delete, echo; the six additive tool families — otp, search, host.crawl / host.exec (via zwire_host::api), run.spawn, and zcite.save; and the download-manager actions dl.add / dl.list / dl.pause / dl.resume / dl.cancel / dl.remove / dl.clear / dl.openDir / dl.openFile / dl.writeFile / dl.writeFileChunk. Downloads run in detached worker processes (--dl-worker <gid>, one per download) that setsid away from the parent, fetch N parallel Range segments with ureq + rustls (no aria2 binary), and persist authoritative state under ~/.cache/zpwrchrome/dl/ so the queue survives browser restarts. pass support also requires GPG configured locally.

userscripts (Tampermonkey-equivalent)

The userscript engine (lib/userscript.js + lib/gm-shim.js) runs scripts in Chrome's native USER_SCRIPT world via chrome.userScripts. It parses the // ==UserScript== metadata block (@match / @include / @exclude, @run-at, @name, …), validates match patterns, and exposes a Greasemonkey-style API. Manage, edit, enable/disable, and watch the injection fire-log in the dashboard at scripts-manager/manager.html (open with the manage-scripts command). Supported GM calls:

Each is also available in promise form (GM.getValue, GM.setValue, …). Per-script values are stored in an isolated chrome.storage.local bag, keyed by script, and dropped when the script is deleted.

permissions

19 permissions are declared in manifest.json. tests/static.test.js enforces that every declared permission is actually referenced in background.js or popup.js — no dead permissions ship.

configuration & storage

No options file and no build step — runtime state lives in chrome.storage. chrome.storage.session holds the cross-window MRU stack (survives service-worker restart, cleared on browser restart); chrome.storage.local holds scenes, installed userscripts, per-script GM bags, the userscript fire-log ring buffer, download settings / rules / queue snapshot, page-theme injector knobs, ModHeader profiles, and pass settings. Browsing history and recently-closed tabs come from the Chrome-managed chrome.history and chrome.sessions APIs. The download host keeps its own authoritative state on disk under ~/.cache/zpwrchrome/dl/.

troubleshooting

• pass / downloads do nothing The native host isn't registered. Run cargo install zpwrchrome-host && zpwrchrome-host --install <ext-id> with your extension's ID (from chrome://extensions, Developer mode), then restart the browser. Chrome reports "Native host has exited" when the manifest is missing or points at a stale binary path.
• pass entries don't decrypt pass support needs GPG configured locally — the host shells out to your GPG agent to decrypt ~/.password-store/*.gpg. Verify pass show <entry> works in a terminal first.
• only 4 commands have default shortcuts Chrome MV3 caps default-suggested keys at 4. Bind any of the remaining 51 commands yourself at chrome://extensions/shortcuts.
• a shortcut doesn't fire The key is reserved by the OS or another extension, or collides with an existing binding. Pick a different chord at chrome://extensions/shortcuts.
• downloads behind a login fail The host forwards Chrome cookies + User-Agent on every request; if a URL still 401/403s, the session cookie may have expired — reload the source page so Chrome refreshes the cookie, then retry the download.

companion theme

The theme/ directory ships a separate Chrome theme that paints the browser frame, toolbar, and new-tab page with the same cyberpunk palette (#05050a bg / #05d9e8 cyan / #ff2a6d accent). Themes cannot be bundled with action extensions, so load it as its own unpacked extension.