The Chrome extension that gets your copied AI answer into PassbackAI in one click
You've got the answer open. Five things need work. You've done this before: copy the answer, open a new tab, find PassbackAI, paste, annotate, copy the feedback block, find the chat tab again, paste, send. Six steps. Two context switches. Every single time.
That friction was never the hard part. But it was the part that made the hard part harder.
PassbackAI for Chrome is a browser extension that intercepts the Copy button on Claude, ChatGPT, Gemini, and Perplexity and shows a small toast: "Copied. Review in PassbackAI →" One click opens a pre-loaded PassbackAI tab. Annotate your passages, copy the feedback block, paste it back into the chat. The round trip that used to be six steps and two context switches is now one click at the start. The extension captures any LLM answer universally, forwards the text directly to passbackai.com, and does all of this entirely in your browser — it holds nothing server-side, and no copied content ever leaves your machine. Install from the Chrome Web Store.
What happens when you click Copy on Claude
You click the Copy button on a Claude response. Nothing looks different at first. Then, a moment later, a toast appears in the bottom-right corner of the screen:
"Copied. Review in PassbackAI →"
Click it. The extension opens a fresh PassbackAI tab with your answer already loaded — the full text, ready to highlight. No paste step. No tab hunt. The context switch is still there in principle; the friction of it is gone.
The toast auto-dismisses after a few seconds if you don't need it. If you close it with the ✕, it stays quiet for the rest of that browser session. It doesn't nag.
What you'll see
- Brand-matched toast, bottom-right. Small, unobtrusive, matches the PassbackAI palette — not a banner, not a takeover.
- Auto-dismiss. It disappears on its own. You don't have to interact with it if you don't need it.
- Session-level silence. Hit ✕ once, it won't appear again until your next browser session.
Where it works right now
The capture-and-forward leg — Copy on any page triggers the toast and pre-loads PassbackAI — is live on Claude, ChatGPT, Gemini, and Perplexity. It also works on any other page where text is copied, because the intercept is universal, not site-specific.
The return trip isn't the missing piece — it already works. Mark up the answer in PassbackAI, copy the feedback block, paste it back into the chat: the same move you've always made, and the one that closes the loop. (When a document reaches PassbackAI through Claude's MCP connection rather than the clipboard, the merged feedback returns to Claude natively, with no paste at all — but that's the Skill & MCP path, not the extension's.) What the extension will add here is convenience: auto-pasting that feedback block into the chat's input field for you. That bridge is wired on the extension's side and waiting for the site to emit the signal. Until it does, you paste it yourself — one step, unchanged.
The universal capture leg already reaches the code tools, too: copy from Cursor, Lovable, or v0 with the extension active and you can forward the text to PassbackAI today. What's not there yet is the branded, automatic toast on those specific sites — their code-output interaction model needs its own tuning. That's the next iteration.
Honest status — what works today
- Capture is live. Copy any LLM answer and the toast appears, universally.
- Forward flow is live. One click on the toast opens a pre-loaded PassbackAI tab.
- Return flow works; the auto-paste convenience is landing. Copying the feedback block and pasting it back into the chat works today, as it always has — and a doc routed in over MCP sends back to Claude natively. The extension is also ready to auto-paste the block for you once the site emits the bridge signal; that half is wired and waiting. Manual paste until then.
- Install: Chrome Web Store → (Published. Free. No account needed.)
The extension exists for the same reason the site exists: stop letting friction be the reason the work doesn't happen. The annotation was never the problem. The six steps before it were. One of them is gone. The rest are on the way — and there's a short under-the-hood piece coming on what the clipboard interceptor, the ?omg-fresh handshake, and the reproducible build actually look like, for those who want to read the mechanism rather than just click it.