更新履歴

Changelog

What's new in Kunkun — feature updates, grammar rule improvements, and bug fixes.

v0.5.1September 10, 2026

Corrections You Can Trust

  • FixedIn Gmail, applying a correction could in rare cases change text next to the error rather than the error itself, and one case was found where a word went missing from a sentence. Every correction is now checked against the document afterwards, and one that cannot be applied cleanly is reported instead of being made.
  • FixedA check that failed could be shown as “No errors found”. A check that does not complete now says so, rather than reporting your writing as clean.
  • FixedGrammar checking could stop after the first check while you carried on typing. Any edit now triggers a re-check — including single-character fixes such as 見れる → 見られる, which earlier versions could not see as a change at all.
  • FixedThe panel could sit on “Kunkun working…” indefinitely if the extension’s background service was interrupted. Checks now give up after a time and show an error you can retry.
  • FixedOn Gmail and Notion, the extension could occasionally fail to start at all, showing nothing on the page.
  • FixedAccepting a correction that could not be applied no longer removes it from the list as though it had been — the error stays until it is genuinely fixed.
  • ImprovedPolish no longer produces double-honorific keigo (二重敬語) such as お置きになられました. Each politeness level now has an explicit register, and formal writing no longer adds honorifics where they do not belong — 尊敬語 describes what the person you are addressing does, never your own actions.
  • ImprovedPolish now works on long documents. It previously refused anything beyond a short passage; it now splits longer text, rewrites it in pieces, and tells you when it will take a moment.
  • ImprovedFix All now tells you when it could not apply anything — for example when the compose window is collapsed — instead of appearing to do nothing.
  • ImprovedIn Gmail your text is now checked once per edit rather than twice, which is faster and uses less of your monthly quota.
  • FixedGoogle Docs add-on: Polish no longer fails in Sheets and Slides. Applying a correction in Slides keeps the surrounding formatting, and selecting an error in Sheets no longer leaves a highlight behind permanently.
v0.5.0September 6, 2026

New Look, Smarter Dashboard & Simplified Navigation

  • NewRefreshed visual design — new color palette and typography across the website and Chrome extension (popup and settings).
  • NewUsage trends on your Account Dashboard — see whether your grammar mistakes are trending up or down over recent weeks, with an at-a-glance sparkline.
  • ImprovedYour Top Mistakes list is now clickable — select any mistake type to filter your History down to just those checks.
  • ImprovedSimplified navigation — Dashboard now lives in the main menu, and the account dropdown is limited to billing.
  • ImprovedHistory page streamlined to focus on grammar checks, with less-useful filters removed.
  • ImprovedRemoved the furigana reading-helper feature — dedicated furigana tools do this better, so we’re keeping Kunkun focused on grammar.
  • FixedJLPT Mode checks are now correctly counted in your usage stats.
  • FixedFixed an issue where the History page could show an error message and a “no history” message at the same time.
v0.4.1April 28, 2026

Shareable Language Links & Landing Page Polish

  • NewShareable language links — append ?lang=ja or ?lang=en to any URL to land directly on that language version.
  • ImprovedLanding page copy refreshed to focus on what Kunkun does for your writing rather than how it works under the hood.
v0.4.0April 10, 2026

Settings Apply Everywhere & Google Docs Improvements

  • ImprovedYour writing style settings — politeness level, writing context, writer mode, JLPT level, and explanation language — now apply to every grammar check across the website, Chrome extension, and Google Docs add-on.
  • ImprovedBatch grammar check now respects your saved preferences for consistent results across all checked texts.
  • ImprovedGoogle Docs add-on now sends all preference settings on every grammar check, including JLPT level and explanation language.
  • NewGmail interface now available in Japanese (日本語).
v0.3.0April 9, 2026

Japanese Native-Speaker Landing Page & Content Polish

  • NewDedicated Japanese-language landing page designed for native speakers — focuses on keigo, business emails, and job hunting scenarios instead of JLPT.
  • NewLanguage-aware routing automatically shows the Japanese or English landing page based on browser language.
  • ImprovedLanding page redesigned with real product screenshots replacing placeholder content.
  • FixedFixed grammar error field names in the Batch processing page.
v0.2.0April 7, 2026

Dark Mode, Bilingual UI & Security Hardening

  • NewFull dark mode support across the entire website.
  • NewComplete English/Japanese bilingual interface — all pages now support language switching.
  • NewGoogle Sign-In — sign up in one click with your Google account.
  • NewCentralized user preferences with a new Settings page that syncs across extension and website.
  • ImprovedPerformance improvements for faster grammar checking.
  • ImprovedSecurity improvements across the platform.
  • ImprovedTrial system redesigned with explicit opt-in and clearer messaging.
  • FixedFixed 404 page, GA4 tracking, dark mode gaps, and sitemap issues.
  • FixedFixed CORS issues with Google Docs add-on token exchange.
v0.1.0April 4, 2026

Initial Beta Launch

  • NewChrome extension with real-time Japanese grammar checking on any website.
  • NewGoogle Docs add-on with dedicated sidebar for document-wide checking.
  • NewGrammar detection for particles, verb conjugations, tense, and sentence structure.
  • NewKeigo and politeness level detection — distinguishes between 丁寧語, 尊敬語, and 謙譲語.
  • NewAccount dashboard with subscription status and trial management.
  • NewSubscription management with free trial.
  • NewPrivacy-first design — text is processed in real-time and never stored.

Have feedback or found a bug? Contact us.