Voyager: A Browser Extension That Adds Folders, Prompt Vault and Export to Gemini, Claude and ChatGPT

The gap Voyager fills in Gemini, AI Studio, Claude and ChatGPT

The stock interfaces of these chat products give you a flat, chronological list of conversations. There is no folder tree, no reliable way to keep a reusable prompt next to the input box, and no first-party export that preserves images. Voyager targets exactly that gap. The README's tagline is "Make every AI chat yours", and its feature table covers Gemini, AI Studio, ChatGPT, Claude, DeepSeek and Kimi, plus a prompt library that works on any other site you add, localhost included.

The intended user is someone with dozens or hundreds of threads rather than a handful. Folders, batch delete, and a prompt library that follows you across products are all answers to the same problem: the chat history is an asset, but the vendor UI treats it as a log.

How the extension is structured: manifest, per-browser Vite builds and a plugin engine

This is a TypeScript extension built with Vite and Bun. The repository root carries a shared manifest.json plus manifest.dev.json, and separate Vite configs per target: vite.config.chrome.ts, vite.config.firefox.ts and vite.config.safari.ts. The package scripts mirror that split, with build:chrome, build:firefox, build:safari and build:edge, and a build:all that chains chrome, firefox and safari. There is also a custom-vite-plugins.ts file and a scripts/ directory, which is where the Safari resource verification and the Edge packaging step live.

Feature code sits under src/, with a Voyager/ directory and a docs/ site alongside. The README describes three layers: one small file per site that says where the sidebar, messages and composer are; primitives such as the timeline, folders, formula copy, diagrams and export; and plugins written as plain JSON that point primitives and CSS at those places. Voyager's own features, including the timeline, formula copy, quote reply and reading width, ship as official plugins, and folders on Gemini and AI Studio are the last piece still running as built-in code. When a site redesigns its page, one file needs fixing, and on ChatGPT, Claude, DeepSeek and Kimi that fix arrives from the plugin catalog without an extension update. The extension is not a proxy. It does not sit between your browser and the model. It runs in the page and reshapes the interface, which is why the README can point to an incident where Gemini made some users' history inaccessible while Voyager users could still see saved conversations in their folders.

Installing Voyager and saving your first prompt

For normal use you install from a browser store rather than from source. The README links the Chrome Web Store, Edge Add-ons and Firefox Add-ons listings, and the homepage at voyager.nagi.fun carries the documentation. After installation, open the extension popup. The README lists visual effects (snow, rain, sakura) as one switch in the popup.

The prompt library and cloud sync work on every supported site and on any other site you add, localhost included. The README's example shows the prompt library inside DeepSeek Harness.

If you want to build from source, the package manager is pinned in package.json and the build scripts are explicit about the target:

bun install
bun run build:chrome

The first command installs dependencies with the pinned Bun version. The second runs the Chrome Vite build. Note that `bun run build` alone is aliased to the Chrome config, so it does not produce a Firefox or Safari bundle. There is a dev mode driven by nodemon configs, for example `nodemon.chrome.json`, and `dev:chrome-open` launches Chrome through a script in scripts/.

What is Gemini-only, what is shared, and where Voyager stops helping

The feature split matters more than the marketing line. The README's table puts folders, the timeline, export, formula copy, quote reply, reading width and typography, Vim keys, the send key and visual effects on ChatGPT and Claude as well as Gemini, most of them as one switch in the popup; diagrams are listed for Gemini and ChatGPT, and batch delete only for Gemini and AI Studio. Gemini alone also gets Deep Research export, watermark-free images, forks, context sync, a default model and a Markdown fix.

The larger limitation is structural. Voyager manipulates the DOM and storage of pages it does not own. The README's own anecdote about Gemini's February 18th incident is a good illustration of the benefit, but the same architecture means a vendor redesign can break a feature without warning, and the extension cannot fix server-side data loss. Cloud Sync is described as going through Google Drive, or iCloud on Safari, so your folder and prompt data leaves the browser in those modes. Treat the local-first framing as the default and cloud sync as an opt-in that changes the threat model.

Voyager compared with a desktop client or a self-hosted chat UI

The obvious alternative is not another extension but a different client entirely: a desktop app or a self-hosted chat front end that stores conversations in a database you control. Those give you a real data model, real search, and export that does not depend on scraping a page. The trade-off is that you lose the vendor's own product surface, including model-specific features and whatever the vendor ships next week. Voyager takes the opposite bet. It keeps you inside Gemini, Claude and ChatGPT and adapts their interfaces, which means you keep every first-party feature but inherit every first-party UI change.

A second alternative, for the prompt manager specifically, is a standalone snippet tool or clipboard manager. Those are more reliable because they do not depend on a host page's DOM, but they cannot inject a prompt list next to the input box of an arbitrary site, which is the specific trick Voyager performs with the DeepSeek Harness example. The extension's own plugin engine sits between these two approaches: it is more structured than a userscript, less isolated than a separate app.

Licence, maintenance and the cost of keeping up with three vendors

Voyager is GPL-3.0, and package.json carries `"license": "GPL-3.0"` with the author listed as Jesse Zhang. There is a THIRD_PARTY_NOTICES.md at the repository root, which is where bundled dependencies and their terms are recorded; read it before redistributing a build. GPL-3.0 matters if you intend to fork and ship a modified extension, because derivative distributions carry the same licence obligations. Nothing here is legal advice, and the repository does not spell out a separate commercial or exception policy.

The repository is not archived, and the last push was on 2026-11-02, the same day as the most recent release, v2.3.1, which was preceded by v2.3.0 on 2026-10-31 and v2.2.1 on 2026-10-24. That cadence is the real maintenance cost signal. Supporting Gemini, AI Studio, ChatGPT, Claude, DeepSeek and Kimi simultaneously means six moving targets plus a plugin catalog, and the release history shows frequent releases rather than long stable cycles. If you pin a version, expect to move off it when a host UI change lands. The repository ships linting, formatting and test tooling (oxlint, oxfmt, vitest), so there is some internal discipline.

Editorial conclusion

Adopt Voyager if you run long Gemini or AI Studio sessions and want folders, a prompt vault and export without handing your chat history to a third-party service. Do not adopt it if you need vendor-sanctioned integrations, an audited security posture, or a guarantee that a UI change at Google or Anthropic will not break a feature overnight. Before installing, check the manifest for the permissions it requests, confirm the current version on the release page, and test one export on a throwaway conversation.

Frequently asked questions

Official sources

1. License: GPL-3.0
2. Nagi-ovo/voyager on GitHub
3. Project website
4. README
5. Releases