Should I vibe code
Rewrite selected sentences for tone, length, fluency, and clarity with side-by-side choices
The rewrite is one prompt. The product is a browser extension that doesn’t eat your cursor in Gmail.
?
Their verdict, the Advanced price and the build-time estimate come from their entry, MIT-licensed. Checked 2026-08-04.
?
Our verdict, the regret score and everything below it. Editorial and unsponsored — nobody can pay to be moved.
The honest answer
why the verdict is what it is
Strip the marketing and Wordtune is: select a sentence, send it to a model with a tone instruction, show ten alternatives, replace on click. That is an afternoon, and your version has a genuine advantage — you choose the model, you write the tone prompts, and your drafts go only where you decided they go. Two honest caveats, neither of them dangerous. Latency is the product: Wordtune returns its list fast enough that you keep clicking, and a version that takes four seconds gets abandoned by you, personally, in week two. And the surface is harder than the feature — living inside Gmail, Google Docs and LinkedIn without wrecking selection, formatting or the undo stack is where browser-extension side projects go to die. Build it as a small editor or a system-wide hotkey first. Extension later, if ever.
What actually breaks
not "if". the specific failures.
- Latency. Ten alternatives in four seconds is a different product from ten in one, and it is the one you quietly stop opening
- Contenteditable. Replacing a selection inside Gmail or Google Docs without destroying formatting, the undo stack or the cursor position is the actual engineering here
- Your API key, if it ever ships inside the extension — an extension bundle is a public file anyone can unzip and read
- The model you pinned, deprecated on a vendor’s schedule, taking the tone prompts you spent an evening tuning with it
- Cost, quietly, if a request fires on every keystroke instead of every deliberate action
- Not much else. This is one of the least dangerous categories on the site, and the verdict reflects that
Is that you?
the verdict is a default, not a law
- It runs on your own text, with your own key, on your own machine
- You want tone presets tuned to how you actually write, rather than a general-purpose “casual”
- You are content to paste into a small editor instead of rewriting in place
- The text belongs to a client under an NDA and you have not read the provider’s data-retention terms
- You intend to hand the extension to other people with your API key inside it
- What you actually need is grammar correctness rather than rephrasing — that is a much older problem and LanguageTool already solved it
If you build it anyway
the checklist, then the prompt that enforces it
- Keys never ship to the client. Proxy through a small server you control, or run a local model.
- Cache on a hash of (text, tone, model). You will rewrite the same sentence six times and should pay once.
- Show the original beside the rewrite and never replace without an explicit click. A silent rewrite loses the nuance you cared about.
- One request per deliberate action, never per keystroke, with a hard monthly spend cap you can see.
- Keep the model ID and prompt templates in config, not scattered through code, so a deprecation is a one-line change.
- Put a line in the README naming which provider your drafts are sent to and what that provider retains. Then read it again before pasting client work.
I am building a sentence-rewriting assistant — select text, get alternatives for tone and length, click to replace. It is genuinely low-risk; the job is keeping it that way.
1. No API key ever ships to the client. Not in a browser extension bundle,
not in a desktop app, not in a config file the user can open. Proxy through
a small server I control, or run a local model.
2. Before any extension work, build a plain editor or a system-wide hotkey
that operates on the clipboard. It is one afternoon, it proves the prompts,
and it does not require fighting contenteditable.
3. If I do ask for the browser extension, replace text through the host page’s
own selection API and preserve its undo stack. Show me the Gmail compose
case and the Google Docs case before styling anything.
4. Never replace text silently. Show original and rewrite side by side and
require an explicit click — a rewrite that changes the meaning is only ever
caught by the person reading it.
5. Cache responses keyed on a hash of (text, tone, model). I will rewrite the
same sentence six times and I should pay once.
6. One request per explicit user action, never per keystroke. Add a hard
monthly spend cap and a visible token counter.
7. Put the model ID and the prompt templates in a config file rather than
through the code. Models get retired and I want to swap one in a minute.
8. Stream the alternatives as they arrive. Perceived latency is the whole
product here; a four-second wait is why I would stop using it.
9. Write a README section naming the provider my text is sent to and its
retention policy. If I mention client work or an NDA, tell me to check that
before writing another line.
10. Out of scope: grammar correction (use LanguageTool), plagiarism checking
(a licensed corpus, not an algorithm), and any kind of account system.That one keeps you out of trouble. For the prompt that actually builds it, canivibecodeit.com has one.
their build prompt ↗Or don’t build it
the boring option, and the way back out
You want it inside every text box on the web tomorrow morning, on someone else’s maintenance budget, without thinking about which model you use or what happens when it is retired. Seven dollars a month is fair for an extension already fixed for every quirk Gmail’s editor has. The DIY version wins on cost, control and privacy; it loses on being everywhere.
$6.99/mo is cheaper than your weekend.
There is nothing to exit. Your text lives wherever it already lived, the tool is a function over a selection, and deleting the repo costs you a config file of prompts you could rewrite in ten minutes. Keep the prompts in version control and they outlive both the tool and the model.
Mature open-source grammar and style checker with desktop and server components.
Questions
Is the rewrite quality really comparable?
Yes, and that is the whole point of this entry. Wordtune’s advantage used to be a specialised model; today a good general model with a well-written tone instruction matches it for most prose. What you cannot match in an afternoon is the delivery — sub-second responses, everywhere you type, with the host page’s formatting intact.
What is the one mistake people actually make here?
Shipping the API key inside the browser extension. An extension is a downloadable archive; a key in it is a key on the internet, and the first sign of trouble is a bill rather than a breach notice. Proxy every request through something you control, even when the only user is you.
Every week, someone ships something they shouldn’t have.
New verdicts, the worst thing that landed in the trap, and the occasional incident report. No other email, ever.
A fiction brainstorming tool is prompts with a nice wrapper. Make it yours.
Twenty-five reports, and most of them are counting things. The one you can’t write is the grammar engine.
A grammar checker you run locally never has to be trusted with what you wrote.
last reviewed 2026-08-04 · verdict is editorial and unsponsored · shared entry data from canivibecodeit under MIT · not legal advice