AI assistants and search decision

Superpower for AI

A single capable developer can build a useful, local browser-extension replacement (folders, prompt library, exports, shortcuts and simple prompt rewriting) in about a week and maintain it cheaply; you’d lose the vendor polish, distribution and built-in Drive sync unless implemented.

Visit website
You pay

$7.99/mo

$96/yr

Read off the official pricing page.

You’d pay instead

$100one-off32 h to build

$0/mo3 h/mo upkeep

On cash alone, building overtakes the subscription at 2 seats.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Inject UI into gemini.google.com to add folders and prompt library, let user save/open prompts, export chat contents to PDF/DOCX/TXT, add keyboard shortcuts and UI tweaks, and implement a local client-side prompt-optimizer (rewrite templates) with optional Google Drive sync via OAuth.

What it still won’t have

  • Polished UI/UX and cross-device license management provided by the vendor
  • Vendor support, refunds handling, and curated feature roadmap
  • Chrome Web Store distribution, reviews, and discovery
  • Built-in Google Drive sync implementation unless you implement Drive OAuth and storage yourself
  • Guaranteed compatibility and timely updates for Gemini UI changes from the vendor

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 2 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a Chromium browser extension (manifest v3) using React for injected UI and TypeScript. Include content scripts that detect gemini.google.com, inject a sidebar and top bar controls, and observe chat DOM mutations. Implement: (1) folders and nested folder UI persisted via chrome.storage.sync (and optional Google Drive sync via OAuth using Google Drive API), (2) prompt library with // slash command quick insert, (3) chat export to TXT/MD/DOCX/PDF using client-side libraries (e.g., html2pdf, docx), (4) keyboard shortcuts configurable in an options page, (5) a client-side Prompt Optimizer module that applies rewrite templates and chains prompts sequentially, and (6) license activation UI storing a local license key. Out of scope: backend licensing server, paid storefront integration, and training models. Provide error handling for DOM mismatch and storage failures, unit tests for core modules, and end-to-end tests simulating gemini.google.com interactions.
How we checked3 sources · 2/3 runs agreed · evidence score 84

How the score was reached

  • Build verdict base78
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Evidence score84

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded