v1.11.0

Added Tone check uses Chrome's Decisions API when it is ready. With chrome://flags/#decisions-api (developer trial, Chrome 158 Dev/Canary) and its model already downloaded, the tone check first asks DecisionModel one choice question (positive / neutral / negative / toxic), which answers without generating text. A positive or neutral verdict with at least 60% confidence is the whole result, so the Prompt API is not called. Negative and toxic verdicts still go through the Prompt API for the explanation and rewrite suggestion; a toxic verdict colors the badge first. Without the API, before its model is downloaded (Comment Vibe never starts that download: create() needs a user gesture), on low confidence or on an error, the tone check uses the Prompt API as before, and re-checks the Decisions API at most every 10 minutes. Checked on Chrome 158 Canary: DecisionModel ( availability , create , decide , destroy ) is exposed to extension content scripts with the flag, and create() rejects with

https://github.com/dzienisz/comment-vibe/releases/tag/v1.11.0↗
Share on XShare on LinkedInShare on Bluesky
Kamil Dzieniszewski

Kamil Dzieniszewski

@dzienisz

🇵🇱 PL · Warsaw

I'm a Senior/Lead Frontend Developer in Warsaw (React, TypeScript, Next.js) who builds AI-native. On the side I ship small, privacy-first...

Available for work
Comment Vibe
Comment Vibe

Comment Vibe

Private, on-device AI tone checker for your comments.

Cookies & privacy

We use cookies to keep the site working, measure traffic, and show relevant content. You can choose which categories to allow. Details in our Privacy Policy.