v1.10.0

Added Tone check asks for greedy sampling, ready for Gemma 4 Multi-Token Prediction (MTP). Chrome Canary's MTP developer trial ( chrome://flags/#on-device-model-speculative-decoding ) only speeds up sessions created with samplingMode: 'most-predictable' , so the tone-check session now requests it first. If a build rejects the option, the session is retried with the previous options, and the rest of the fallback chain is unchanged. The rewrite session keeps default sampling, since greedy rewrites tend to repeat themselves. Checked in Chrome 155 and 156 Stable and 158 Canary: without an origin-trial token, create() ignores samplingMode without an error in web pages, extension pages and content scripts alike. It only reads the option with chrome://flags/#enable-experimental-web-platform-features , and then rejects invalid values with a TypeError . Playground: MTP note and Prompt API measurement. The Prompt API page explains MTP, the Canary flags for a before/after comparison ( #on-device-

https://github.com/dzienisz/comment-vibe/releases/tag/v1.10.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.