Browser extension (internal)
Browser extension (internal)
Browser extension (internal)
The GTM Tools browser extension lets each member of a workspace share their authenticated browser sessions (Google, LinkedIn, Reddit) with GTM Tools. The backend pools them per workspace and rotates across the team (round-robin with per-session backoff) for tools that need a real logged-in session.
Cross-platform, cross-browser. Install on any OS, in any Chromium-family browser:
Any other Chromium fork still works for manual load-unpacked + WorkOS
sign-in — the one-click Update / CLI-bridged sign-in features just need the
gtm-tools CLI installed (which acts as
the native-messaging helper) and a browser whose native-host directory or
registry path the installer recognizes.
The more members connect, the more sessions the rotator can spread load across — which raises both throughput and coverage (a single session rate-limits under volume; a pool does not).
Internal tool. It reads session cookies (incl. li_at, SAPISID) and sends
them to the GTM Tools backend, which can then act as you on those sites. It is
not published to any web store and is distributed only as a private,
repo-gated sideload. Only install it for your own workspace.
It’s not on any web store (stores reject extensions that read session cookies).
Run this in a terminal — no Node, no dependencies, just curl:
It downloads the build into a stable folder, ~/GTM Tools/extension. Then
in Chrome (once — the path never changes):
chrome://extensions (Edge: edge://extensions, Brave: brave://extensions).~/GTM Tools/extension.When a new version ships, the popup shows an “Update available · v0.x.x”
banner at the top. One click — the gtm-tools CLI
acting as a native-messaging helper downloads the new build into the same
stable folder and reloads the extension. No terminal, no re-curl.
If you installed only the extension (no CLI yet), re-run the same curl command
to pick up the new version, then click the reload icon on the extension card
in chrome://extensions:
The one-click Update path requires the gtm-tools CLI
installed (it’s the native-messaging helper). Install once with
curl … /cli/install.sh | bash, then both the CLI and the extension
update themselves from then on — terminal-free.
Prefer to do it by hand? Download the build and load it unpacked. Updates are manual (re-download, replace the folder, reload).
chrome://extensions (Edge: edge://extensions, Brave: brave://extensions).about:debugging#/runtime/this-firefox.manifest.json inside the unzipped folder.
(Temporary add-ons are removed on restart; a signed build is needed for a
permanent install — see self-hosted below.)Loading unpacked is per-person and updates are manual. For zero-touch install across a team on managed devices, host the packaged build yourself — no web store involved:
.crx + an update.xml
on your server and force-install via the ExtensionInstallForcelist policy
(Google Workspace Admin console, or Intune / GPO / macOS plist). It installs
silently for everyone in the org and auto-updates. Chrome blocks self-hosted
.crx on unmanaged browsers, so this path requires managed machines.Have teammates install + connect too — each contributes their sessions, giving the workspace more sessions to rotate across.