On-device Chrome AI only
Uses Chrome built-in Prompt/Writer APIs. No API keys, no FuriaHub proxy, no third-party LLM hosts.
SoonV3
Mail Draft Next
Mail Draft Next injects into Gmail compose and generates tone-matched drafts using Chrome’s on-device Prompt/Writer APIs. Your mail never goes to a FuriaHub or third-party LLM proxy. Requires a Chrome build with on-device AI available.
Coming soonAll extensions
Mail Draft Next
Gmail drafts via on-device Chrome AI
Features
What you get in practice — not just a checklist.
Gmail compose integration
Adds a draft assistant to compose and reply windows on mail.google.com.
Tone and length controls
Neutral, friendly, formal, or concise — short through long — with multiple variants.
Thread-aware context
Optionally reads the subject and quoted thread so replies stay on topic.
Clear capability gating
Shows Ready, Downloading, or Unavailable with setup steps instead of failing silently.
Local draft cache
Optional recent drafts stay on device with a capped history.
Privacy
Settings are stored locally. Details are on the Privacy Policy page.
Permissions
storageactiveTab
FAQ
Common questions about Mail Draft.
Why does it say Unavailable?
Chrome on-device AI must be present and the model downloaded. The popup lists setup steps when the Prompt API is missing.
Do my emails leave the device?
Mail Draft Next does not send mail to FuriaHub or a cloud LLM API. Generation uses Chrome’s on-device model when available.
Blog
Guides and tips for getting more out of Mail Draft.
Gmail drafts without cloud API keys
On-device Chrome AI keeps the drafting loop inside the browser.
Mail Draft Next is intentionally narrow: Gmail only, on-device only, with honest capability status.
If your machine cannot run the model, the extension tells you instead of quietly doing nothing.
Recommended extensions
V3 · v0.1.1
JSON Formatter Next
Beautiful JSON right in the browser
DeveloperProductivity
V3 · v0.1.1
Script Monkey Next
Userscript manager for Manifest V3
DeveloperProductivity
Message on Telegram