Switch AI tools. Keep the work moving.

EXAMPLE · CHATGPT → CLAUDE

A useful handoff makes the next step clear.

Objective: Finish the checkout screen.

Pinned constraint: Keep the approved price at $29. No new dependencies.

Next action: Review the error states before writing code.

Source messages remain labelled. Assistant claims are unverified. Omitted context is disclosed.

Install in your browser

Site layouts change. Capture reads loaded text only, not attachments, images, hidden branches or unloaded history. Perplexity, Grok and DeepSeek may require selected text or paste when role labels are unavailable. If a composer cannot be identified safely, use Copy and paste manually. Authenticated site testing is required before the store release.

Local capture, pins, masking, whole-message compaction, save/export and guarded insertion are shared across all four desktop browsers. On-device AI summaries require a compatible Chrome 138+ desktop and English text; availability is checked in the workspace. Chrome may download a model first. Other browsers keep offline compaction, with no cloud fallback. Mobile browsers are outside this first release.

Publish on the Chrome Web Store

This is the publisher checklist. The beta ZIP is ready to download; store submission and approval are still pending.

1. Test the unpacked extension. Check capture against the visible source on all six platforms, tab switching, append/replace/undo, offline compaction, local AI availability, exact pins, masking, export and deletion. Compare long chats with their source; unloaded history is excluded. Test valid and invalid Pro keys separately.
2. Build the release ZIP. Run npm run test:extension, npm run build and npm run extension:package. Upload only promptvibe-extension-1.0.0.zip, which has the manifest at its root.
3. Register a publisher. Open the Chrome Web Store Developer Dashboard, complete account verification and the registration payment shown, then choose New item and upload the ZIP.
4. Complete the listing. Add an accurate name, description, support and privacy links, the included 128 px icon, a 440×280 promotional tile, and actual screenshots at 1280×800 or 640×400. Avoid full-history or guaranteed-accuracy claims.
5. Complete privacy and test instructions. Explain storage, sidePanel and access to the named AI sites. Disclose local chat text, the optional Pro key and explicit cloud Coach/Optimize processing. Explain local model downloads. Give reviewers a non-sensitive demo and dedicated Pro access through the dashboard’s private test field.
6. Submit for review. Choose visibility and regions, resolve all dashboard warnings, then submit. Use deferred publishing if you want to release manually after approval. Google controls review timing.
7. Enable installation for Chrome, Edge and Brave. After approval, configure the actual listing URL in NEXT_PUBLIC_CHROME_EXTENSION_URL and rebuild/deploy. All three use this Chrome Web Store listing. Edge users may need to allow extensions from other stores. The homepage promotion already links here.

Google’s publishing guide · Image requirements · PromptVibe privacy policy

Publish a signed Firefox release

Firefox requires its own manifest and Mozilla signing for permanent installation. The unsigned test ZIP is ready; signing and publication are pending.

1. Verify Firefox 140+. Download and temporarily load the Firefox build using the steps above. Check sidebar tab switching, all six chat platforms, clipboard copy, offline compaction, draft guards, undo, save/delete and optional cloud tools.
2. Build both release packages. Run the checks above and npm run extension:package. Upload promptvibe-extension-1.0.0-firefox.zip to Mozilla.
3. Create an AMO submission. Sign in to Mozilla Add-ons Developer Hub, choose Submit a New Add-on and choose distribution On this site for a public listing with a simple Add to Firefox install button.
4. Complete listing, privacy and review. Add screenshots, support/privacy URLs and non-sensitive reviewer instructions. Explain the local sidebar workflow, clipboard-write permission and supported-site access. The manifest declares authentication information, personal communications and website content because explicit Coach/Pro requests can transmit a chosen draft and API key. Complete all validation and source-code requests.
5. Wait for Mozilla review and signing. After approval, install from the actual AMO listing. For direct private distribution, use Mozilla’s self-distributed signing flow and distribute its signed XPI. An unsigned ZIP cannot provide permanent installation in standard Firefox.
6. Enable the Firefox install button. Set the actual AMO listing URL in NEXT_PUBLIC_FIREFOX_EXTENSION_URL, rebuild/deploy, and verify the homepage → extension page → Add to Firefox flow.

Mozilla signing guide · Firefox data-consent requirements

Where your data goes

Captured sources stay in workspace memory; only handoffs you explicitly save enter local extension storage. Compaction, masking and Chrome AI summaries run on this device. Chrome may download its AI model; summary input is processed locally. Saved cards are not encrypted. The extension contains no analytics.

Opening Context does not fetch the library or send chat text. Opening My prompts loads the public library, or private tasks and profiles with a saved Pro key. An explicit Coach or Optimize action sends the draft you choose to PromptVibe and its AI provider, OpenRouter. Context Bridge does not send transcripts to that service.

If you insert or paste a handoff and send it in an AI chat, that platform receives it under its own data policies. Downloads and copied text remain outside the extension after deletion.

Read the privacy policy · Get support · Use the web handover tool