FluidEdits questions, answered.

FluidEdits is a browser extension (Chrome / Chromium / Firefox) that helps you turn on-page UI feedback into clear instructions for your coding agent. You point at (or circle) part of a page, speak what you want changed, and FluidEdits turns that into structured edit requests your workflow (for example Cursor or any AI-assisted editor) can consume.

Developers and designers iterating on web UIs who already use an AI IDE or agent.

Teams building internal tools or customer-facing sites where "change this button / this banner / this copy" is faster said than typed.

1. Open the page you're working on (local dev server, staging, or any URL you're allowed to use).
2. Use FluidEdits to select the UI area and record a short voice note describing the change.
3. FluidEdits uses AI to produce a concrete instruction tied to that UI.
4. FluidEdits copies the result to your clipboard so you can paste it into your editor or agent.

• A supported browser — Google Chrome; other Chromium-based browsers including Microsoft Edge, Opera, Brave; and Mozilla Firefox.
• The FluidEdits extension — Chrome Web Store when available, or an unpacked build for internal / beta testing.
• A valid license (see Licensing below) once you're off the 7-day free trial.

FluidEdits is sold through Lemon Squeezy. Every new user gets a 7-day free trial; after that you continue on one of three license plans launching with the May 30, 2026 beta.

FluidEdits copies a structured text prompt to your system clipboard. Open your AI chat, terminal, or IDE, then paste (for example Ctrl+V / Cmd+V). The extension does not edit your repository by itself — you (or your agent, after you paste) apply the change.

No — anything that accepts pasted text is fair game: Cursor, VS Code, Lovable, cloud IDEs, or a simple text file. Paste where your workflow lives.

The extension targets the Chromium extension platform (Manifest V3): Google Chrome, Microsoft Edge, Opera, Brave, and other Chromium-based browsers.

Mozilla Firefox is supported via a compatible WebExtensions build.

Safari does not support Chrome-extension packages; use a Chromium- or Firefox-based browser for FluidEdits.

We're still in beta — you can install an unpacked build for testing or follow updates on the site. Once the listing is approved, this will point at the live store page.

1. Open Chrome → Extensions.
2. Turn on Developer mode.
3. Click Load unpacked and select your FluidEdits build folder.

For detailed steps, see project docs on GitLab.

To let you mark up your own dev and staging pages, the extension needs permission to run on the URLs you use. We aim for the minimum access necessary for that workflow.

More detail lives in our Privacy Policy.

Purchases and subscriptions are managed in Lemon Squeezy — use the customer portal or links from your order email.

Email contact@fluidedits.com

We aim to reply within 2 business days (often sooner).

After purchase, Lemon Squeezy sends a receipt email with access to your license. You can also find the license in your Lemon Squeezy customer portal.

Open the FluidEdits extension popup → License key → Activate.

• Internet connection and that our backend is reachable.
• Correct license key (copy/paste carefully — no extra spaces).
• If you recently changed devices or hit activation limits, use Lemon's license management to deactivate old devices.

That depends on your Lemon Squeezy license (activation limits). Check your order or the merchant policy on your receipt.

• Check microphone permission in Chrome for the extension / site.
• Use a normal tab — chrome:// pages won't work.

• Re-capture with a tighter selection.
• Speak concretely: "Change the headline to X", "Make the button primary blue".
• If extension UI appears in the screenshot, recapture without overlay chrome in the frame.

If you ship a new build with a different embedded backend URL, users typically need the new package — reinstall or update to the matching build.

To interpret your intent, FluidEdits may send cropped screenshots, audio of your voice note, and technical context about the selected element to our secure server, which forwards allowed requests to the AI provider. We do not put merchant AI keys inside the extension.

See our Privacy Policy and Terms of Service for the current policy on retention and use of captures and prompts.

If we use Google Gemini, their terms apply to the provider side — see Google AI / Gemini terms.

FluidEdits focuses on what you see in the browser and the instructions sent to your agent. It does not automatically upload your full repository.