Integrations

Browser extension (internal)

Pool your workspace's authenticated browser sessions for GTM Tools

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:

OSOne-line installOne-click in-popup updatesOne-click sign-in (no second login)
macOS✅✅✅
Linux✅✅✅
Windows✅✅✅
BrowserTested onNotes
Chromemac · linux · winStandard Chromium native messaging
Edgemac · linux · winIdentical to Chrome under the hood
Bravemac · linux · winSame
CometmacPerplexity’s Chromium browser
ArcmacSame
Vivaldimac · linux · winSame
OperawinRegisters via the Opera-Stable HKCU subkey

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.

Where it’s used

SessionPowersStatus
Googleget_email, which verifies Google Workspace mailboxes via People-PA (no sending)live
LinkedInthe LinkedIn write tools (send_linkedin_message, send_linkedin_invitation) and personal read tools (list_linkedin_conversations, list_linkedin_saved_posts, list_user_posts), session instead of the old cookie scriptlive
Redditthe full Reddit toolset: read posts and comment trees (get_reddit_post), post and comment (create_reddit_post, create_reddit_comment), vote (vote_reddit), read the inbox (list_reddit_inbox), and DM users via Reddit Chat (send_reddit_message)live

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.

Install

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):

$curl -fsSL https://api.gtm-tools.sh/extension/install.sh | bash

It downloads the build into a stable folder, ~/GTM Tools/extension. Then in Chrome (once, since the path never changes):

  1. Open chrome://extensions (Edge: edge://extensions, Brave: brave://extensions).
  2. Turn on Developer mode (top-right).
  3. Load unpacked → select ~/GTM Tools/extension.
  4. Click the GTM Tools icon and press Connect.

Updating

When a new version ships, the popup shows an “Update available · v0.x.x” banner at the top. One click, and 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:

$curl -fsSL https://api.gtm-tools.sh/extension/install.sh | bash

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.

Manual install

Prefer to do it by hand? Download the build and load it unpacked. Updates are manual (re-download, replace the folder, reload).

  1. Download chrome-mv3-prod.zip and unzip it.
  2. Open chrome://extensions (Edge: edge://extensions, Brave: brave://extensions).
  3. Enable Developer mode (top-right).
  4. Load unpacked → select the unzipped folder.

We don’t ship a Firefox build today. The extension is packaged as Chrome MV3, and the Chromium-based browsers above (Chrome, Edge, Brave, Arc, Vivaldi, Comet) all load it. If you need Firefox, see the signed-XPI note under self-hosted rollout below, and tell us so we can prioritise it.

Self-hosted rollout (optional)

Loading unpacked is per-person and updates are manual. For zero-touch install across a team on managed devices, host the packaged build yourself, with no web store involved:

  • Chrome / Edge / Brave (managed only): host the .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.
  • Firefox: get the XPI signed by Mozilla as “unlisted” (no public listing, no review), host the signed XPI + update manifest, and Firefox installs and auto-updates from it. This works on regular, unmanaged Firefox.

Connect

  1. Click the GTM Tools extension icon.
  2. Connect with WorkOS and sign in with your workspace email.
  3. The extension captures your current Google / LinkedIn / Reddit sessions and syncs them to your workspace pool. It then re-syncs the instant a session token rotates (Google cycles its tokens every few minutes), so the pool always tracks your live browser. The popup shows which sessions are shared.

Have teammates install + connect too. Each contributes their sessions, giving the workspace more sessions to rotate across.