Researching across thirty tabs, copying fragments into a scratchpad, then watching half of them vanish by Friday is not a memory problem — it is a tooling problem. Here is how to put a quiet capture layer between your browser and your AI assistant, so what you grabbed at 10am is still there at 4pm, bundled and ready to send.

The "I'll save it later" lie

You open a doc and copy a paragraph. Another tab, a code sample. A Stack Overflow answer, a snippet. A GitHub README, the config block. By the time you have what you need, the clipboard has been overwritten ten times and the only thing you still have is whatever you copied last.

The story you tell yourself is that you are about to paste everything into a scratchpad. The reality is the next idea is already pulling and the snippet gets one second of clipboard life before the next arrives. By Friday, half of what you needed is gone.

Three flavors of that pain show up over and over:

• Stripe webhook research — eight tabs across Stripe docs and a Stack Overflow answer on signature verification. The two lines that solved it were copied at minute three and lost by minute fifteen.
• Tailwind class hunting — you copy the right utility chain for a card, switch to the playground, and by the time you open your editor the copy has been wiped by a button label.
• Debugging a third-party SDK — the error message, the GitHub issue thread, and the workaround snippet were all copied within four minutes. None are reachable at the next standup.

The cost is not the snippets — it is the rebuild. Reopening tabs you already closed, re-running the same query, re-reading the same paragraph twice. Most "research is hard" days are research-twice days, and the second pass burns the afternoon.

What auto-capture actually means

Most Chrome users assume clipboard managers are a macOS dock thing — a hotkey that pops recent copies. That assumption is out of date.

A modern Chrome extension can listen for the standard copy event in any tab and store the selection locally — silently, no popup, no extra keystroke. That is what the ClipGate browser extension does. Every Cmd-C / Ctrl-C in a regular tab becomes a stored, classified entry. Three capture modes fit different research styles.

• Auto mode (default). Every text selection you copy is saved to the local store. You change nothing about how you read. The badge ticks up by one each time.
• Right-click "Save to ClipGate". Highlight a selection on any page, right-click, choose Save to ClipGate. A deliberate save for when auto-capture is off or you want to grab something without overwriting your clipboard.
• The Ctrl+Shift+S shortcut. Same outcome as the right-click entry, faster. Select text, hit the shortcut, the snippet lands with source URL and content-type tag attached.

Selective mode is a feature, not a workaround. During long form fills, onboarding flows, or screen shares, selective mode keeps the store clean. Switch modes from a dropdown in the popup.

Equally important is what auto-capture does not grab. Password fields are excluded by Chrome's permission model. Incognito tabs are out of scope. If a captured value looks like a credential, it is detected, encrypted with AES-256-GCM, masked in the UI, and auto-expired on a timer.

Install the extension in 60 seconds

Sixty seconds, three steps, then you forget it exists until the first time it saves your afternoon.

1. Open the Chrome Web Store listing. Visit the ClipGate extension page, click Add to Chrome, confirm permissions. Works in any Chromium browser — Chrome, Edge, Brave, Arc.
2. Pin the icon to the toolbar. Open the puzzle-piece menu, find ClipGate, pin it. The badge ticks up every time a new snippet is captured.
3. Trigger your first capture. Select any sentence, press Cmd-C or Ctrl-C, click the icon. Your selection is at the top of the list with source URL and type tag attached.

After a single capture, the popup shows the snippet preview, source domain, timestamp, and a Local only indicator. No account prompt, no cloud round-trip. Next time you wonder "did I copy that earlier?" the answer is one click away.

The research-to-AI loop, end to end

You are about to write a Stripe webhook handler. You spend an hour reading across eight tabs — webhook docs, signature verification, SDK reference, two GitHub examples, a Stack Overflow thread on idempotency. Across that hour you copy six snippets: a code block, a JSON payload, an error, a CLI command, a config line, and a URL.

Without auto-capture, you arrive at your editor with one of those six on the clipboard and a foggy memory of the rest. With it, all six sit in your local store, tagged by type and source URL.

Option A — Browser only. Open the popup, multi-select the six snippets, copy as one bundled block. Paste into a new conversation at claude.ai or chatgpt.com. The model has the verbatim docs context with source URLs intact.

// Paste from the popup:
[code]  const sig = req.headers['stripe-signature'];
        stripe.webhooks.constructEvent(body, sig, secret);
        // src: stripe.com/docs/webhooks/signatures

[json]  {"type":"payment_intent.succeeded","data":{...}}
        // src: stripe.com/docs/api/events/types

[error] Webhook Error: No signatures found matching...
        // src: github.com/stripe/stripe-node/issues/1234

Option B — Terminal bundle. If the ClipGate CLI is installed, browser and terminal captures share one local store. One command bundles the last thirty minutes into a Markdown block with classified types and redacted secrets.

$ cg pack --last 30m
# 4 url, 2 code, 1 json, 1 error, 1 command
# 6 snippets · sources preserved · secrets redacted
...
$ cg pack --last 30m | claude "write a Stripe webhook handler"

The win is not that the model is smarter. It is that the model finally sees the same context you saw. Without the bundle, you paraphrase and the model fills gaps from training. With it, the assistant reads the exact docs and the exact error you read at minute four. The handler it writes references the right event types, the right header name, and the idempotency pattern the docs prescribe — because that is the corpus you showed it.

Generalises beyond Stripe. OAuth scopes, infra rollouts, library upgrades — anything where the answer lives across many sources. Auto-capture turns a reading session into a single block, no extra effort.

The right-click escape hatch

Auto mode is the default because most copies during research are worth keeping. Some sessions are not — long form fills, screen shares, onboarding where you paste personal information. For those, switch to selective mode from the popup. Ordinary copies stop landing in the store. To save deliberately:

• Right-click → Save to ClipGate. Highlight, right-click, pick Save to ClipGate. The selection lands with page URL and an inferred type tag — code, JSON, URL, error, or plain text.
• Press Ctrl+Shift+S. Same outcome, no mouse. Works in both modes, so it is also a good "definitely keep this" tap inside auto mode.

The split matches how research feels. Reading is wide — capture everything, prune later. Writing is narrow — only the snippet you are about to use. Switching modes is one click.

Privacy: what's stored, what stays on your machine

The fast version: nothing leaves your laptop unless you explicitly send it.

• Storage is local to your browser profile. Snippets live in the extension's local storage on disk. Not synced to a Chrome cloud account, not shipped to any backend, not visible to other extensions. Uninstalling clears the store.
• Zero network requests for capture or retrieval. No telemetry beacon, no error reporting endpoint, no analytics ping. Popup, badge, and right-click entry run on local code only.
• Secrets are encrypted and auto-expired. Anything that looks like a token, key, or credential is detected at capture, encrypted with AES-256-GCM, and auto-expired on a configurable timer (default two hours, max two days). The popup does not surface secret values in the clear.
• Incognito and password fields are excluded. Chrome's permission model keeps incognito windows out. Password fields never reach the extension. The text you most want kept out of any store stays out.
• Outbound only happens when you choose. Research touches a model the moment you paste into Claude or ChatGPT, or pipe a CLI bundle to the assistant. Until then, every snippet stays local.

Stricter requirements? If your team has air-gapped machines or a no-extensions policy, the CLI alone covers the terminal-side capture story.

When to use the CLI vs the extension (and when both)

The two surfaces solve overlapping but distinct problems. The extension captures from the browser. The CLI captures from the terminal and adds a retrieval and bundling layer on top. Most readers want both.

If torn, install the extension first. Most readers add the CLI within a week — the moment you want to pipe a bundle into claude is when the second half of the workflow clicks.

For the terminal side, see stop losing errors, commands, and paths. Same store, different entry point.

FAQ

Can a Chrome extension really auto-save everything I copy?

Yes. ClipGate listens for the standard browser copy event and captures into a local store the moment your selection lands on the clipboard. No polling, no remote server.

Will it capture passwords or incognito content?

No. Password fields are excluded by Chrome's permission model, and incognito windows are out of scope by default. Credentials that do appear are detected, encrypted with AES-256, masked, and auto-expired on a timer.

How do I get my snippets into Claude or ChatGPT?

Browser-only: open the popup, multi-select snippets, copy as one block, paste into the model. With the CLI: run cg pack --last 30m to emit a Markdown bundle ready to pipe into claude or paste into chatgpt.com.

Does anything leave my machine?

No. Zero outbound network requests. Snippets are stored locally, secrets are encrypted at rest, and there is no cloud sync, no telemetry, no account.

What if I don't want every copy captured?

Switch to selective mode. Auto-capture is off; snippets save only when you right-click a selection or press Ctrl+Shift+S.

Will it work in Edge, Brave, or Arc?

Yes. Any Chromium-based browser supports it, with identical auto-capture, right-click entry, and Ctrl+Shift+S shortcut.

Install ClipGate and stop losing research

Install the extension before your next reading session. Pin the icon, and let the next thirty minutes of research land in a real store instead of one overwritten clipboard slot.

Install the extension from the Chrome Web Store:
https://chromewebstore.google.com/detail/iceplcknbihmnogljpmdhjelckohpice

For terminal-side bundling, also: curl -fsSL https://clipgate.github.io/install.sh | sh

Originally published on the ClipGate blog.