v0.3.1

Fixed

• Compose to new contacts — sending a first message to a recently connected
  person no longer fails with a misleading "not connected" error. The
  createMessage payload was missing a required field (hostRecipientUrns).

How to update

1. Download the .zip asset from this release and unzip it (replace your existing inflow folder, or unzip a fresh copy).
2. Open chrome://extensions, find inflow, and click the reload icon (↻). If you unzipped to a new folder, use Load unpacked and select it.

Prefer building from source? Run git pull && npm install && npm run build, then reload at chrome://extensions. Your conversations and settings are preserved across updates.

Not sure where inflow is installed? Open chrome://extensions (turn on Developer mode) — the inflow card shows the folder it's loaded from.

Full Changelog: v0.3.0...v0.3.1

v0.3.0

Added

• Check for updates command in the command palette (Cmd+K) for an on-demand
  release check.
• The running version is now shown on the keyboard shortcuts bar.

Fixed

• Update checks now run reliably — the GitHub API host is declared, so the
  background check is no longer blocked.
• The ? (shortcuts) and ! (mark as spam) shortcuts now work on non-QWERTY
  keyboard layouts such as AZERTY. Thanks @qchuchu (#4).

Removed

• The WhatsApp community top banner — the button in the conversation header
  already covers it.

What's Changed

• Fix "!" mark-as-spam shortcut on non-QWERTY (AZERTY) keyboards by @qchuchu in #4

New Contributors

• @qchuchu made their first contribution in #4

Full Changelog: v0.2.0...v0.3.0

How to update

1. Download the .zip asset from this release and unzip it (replace your existing inflow folder, or unzip a fresh copy).
2. Open chrome://extensions, find inflow, and click the reload icon (↻). If you unzipped to a new folder, use Load unpacked and select it.

Prefer building from source? Run git pull && npm install && npm run build, then reload at chrome://extensions. Your conversations and settings are preserved across updates.

Not sure where inflow is installed? Open chrome://extensions (turn on Developer mode) — the inflow card shows the folder it's loaded from.

v0.2.0

First public GitHub release, with in-app update notifications.

Important

Existing users: this is a one-time fresh start. This build pins a stable
extension ID so all future updates preserve your data. Moving from an older
build changes the extension's identity once, so inflow will open empty —
re-enter your Gemini key (if you use AI features) and let it re-sync. This
only happens this once; every release after this keeps your data.

Added

• Update notifications — inflow now checks GitHub for new releases and shows
  a banner with a link to the release notes when an update is available.
• GitHub Releases — each version ships a downloadable inflow-<version>-chrome.zip.
• Stable extension ID — updates (zip download or rebuild) now preserve your
  conversations and settings regardless of where the extension folder lives.
• New envelope app icon.

Fixed

• New conversations started from another device (e.g. your phone) no longer show
  the participant as "Unknown".
• A conversation read on another device now reflects as read in inflow, even
  while the realtime connection is active.