bwat 0.21.0

[0.21.0] - 2026-11-12

Added

• Admin: Settings, Data is now Retention. Under it, Keep untouched cards open chooses Forever (the default) or Close after a number of days.

Changed

• Cards: a live card nobody acts on no longer closes after 10 days unless an admin chooses a number of days in Settings, Retention. With a span set, the card still says "Closes in N days" over its last 5.
• cards: a merge (Merge now or the clean-up after the meeting) where only one card has an owner now goes ahead, and the card kept takes that owner; two cards owned by different people are still never merged.

Fixed

• Admin: Settings, Models no longer marks Deepgram as required. Transcription runs through OpenRouter by default, so only the OpenRouter key is.
• Board: picking Today or This week says how many meetings are on screen, instead of listing every meeting's name under the heading.

bwat 0.20.1

[0.20.1] - 2026-11-10

Changed

• setup: docs/plugins.md covers the board plugins only, and links to the bwat plugin README for the agent plugin.

bwat 0.20.0

[0.20.0] - 2026-11-09

Changed

• setup: docs/onboarding.md opens by asking where bwat runs, and wherever this computer and a cloud server differ, a step shows the two side by side in Local and Production columns.
• setup: each production vendor page is visited once: the event secret is copied while the main Zoom app is open, the board's Zoom settings join the account settings table, and the Server-to-Server step, which automatic joining needs, comes before the board app.
• setup: repeated text has one home: the first meeting and the list of what you need come from the master in docs/setup-with-claude.md, and "Who can sign in" sits next to sharing bwat.
• setup: a new docs/plugins.md lists the Claude Code plugin and the board plugins, and how each is turned on.

bwat 0.19.0

[0.19.0] - 2026-11-09

Added

• web: hovering a card's meeting name underlines it; clicking filters the board to that meeting.

Changed

• backend: "Join meetings on its own" starts off; an admin turns it on in Settings once the setup checks pass. An install that never saved it now stops joining on its own; one that saved it on keeps it.

Fixed

• setup: the onboarding guide names the board's Invite bwat and the admin panel's Faster cards, and says the setup page deletes bwat.answers by itself.
• setup: the onboarding guide says which Docker each tier needs (Compose 2.1 or later on a server) and that a production install sets BWAT_MODE=production.
• setup: the onboarding guide says only a proxy on the same server reaches the edge port, and how the SDK file and the Zoom manifests move to and from a server.

bwat 0.18.0

[0.18.0] - 2026-11-06

Added

• web: a card Claude has read offers Done on the card itself, without opening it.
• web: a card's receipt names its session: Queued for , then Read by .

bwat 0.17.1

[0.17.1] - 2026-11-05

Fixed

• setup: the test values for secret masking no longer look like real OpenRouter or Google keys, which kept the first public publish from going out.

[0.17.0] - 2026-11-04

Added

• web: a closed card's ⋯ menu offers Reopen in place of a disabled Edit.
• bwat names its licensor in LICENSE and "license": "Elastic-2.0" in its npm package files, and lists the third-party code it carries in THIRD_PARTY_NOTICES.md.
• setup: the Server-to-Server app's steps add the scope user:read:user:admin, needed to link a Zoom account to a bwat account by email.
• backend: when a member joins a meeting, bwat links their Zoom account to their bwat account by email, once Zoom confirms the email.
• backend: an unconfirmed email, or a Zoom account already linked to another member, is never linked.
• admin: the Zoom access check suggests adding the user:read:user:admin scope; automatic joining keeps working without it.
• setup: the guide shows a screenshot of the Meeting SDK download.
• web: adding or editing a goal has a description box, four lines tall and drag to resize, with a gentle tip to make goals SMART.

Changed

• setup: the README fits on one screen, every guide opens with the same sentence, and the onboarding guide drops setup-page lines, repeated dates and secret notes; it shows the first card to expect and what to do when the plugin install fails with "Host key verification failed".
• bot: posting in the meeting chat (the agenda on joining, the five-minute warning, ⏰) is off by default; an admin turns it on in Settings.
• setup, backend, web: the try-it-on-this-computer tier is now called local instead of t0, so the two ways to install read local and production. An install or answers file saved as t0 carries on as local.
• setup: the onboarding guides and the setup page link to, and clone from, github.com/qoralai/bwat.
• setup: docs/hosting.md says what bwat needs from any host (services, Postgres, routing, HTTPS, configuration, secrets, health checks, fleet), for building on your cloud's own services; the production steps link to it.
• cards: The card writer's rules, the same for every window, are now cached on OpenRouter for Claude and OpenAI models, which lowers the cost of sending them again on each window. A new log line shows each answered window's tokens, cache use and cost, so the saving can be measured.
• web: inside Zoom, Settings no longer shows the plugin show/hide switches, and the filters column has no button for them; the full board keeps both.
• setup: the setup page leads; Claude only reads it and answers, and can no longer move it, fill it in or tick a step.
• setup: the guide's Zoom app path follows the Marketplace's new Develop menu (top right).
• setup: the plugin installs from the public marketplace: claude plugin marketplace add qoralai/qoral-plugin-marketplace, then claude plugin install bwat@qoral-plugin-marketplace.

Removed

• bot: the BWAT_PER_PARTICIPANT_AUDIO switch is gone; each speaker is always heard separately, and an install that still sets it starts with a warning.

Fixed

• bot: when the host ends a meeting, the bot finishes the transcript and marks the meeting ended at once, instead of timing out and restarting.
• bot: a meeting app that hangs while leaving is stopped after five seconds, so the bot leaves cleanly.
• backend: the card service stops dialing a bot that has left, gone quiet or lost its meeting.
• bot: a meeting counts as ended only when Zoom's reason says so; when Zoom takes bwat out for another reason, the meeting stays open until Zoom ends it.
• bot: when Zoom puts bwat in a different sitting of a meeting than the one it was sent to, bwat leaves without marking the meeting ended.
• web: picking the session a card is already Queued for says so and sends nothing; Send again on the receipt still sends it again.
• setup: the guide names the admin panel's Overview, Members and Settings tabs for automatic joining and invites.
• web: an open card's Send to Claude receipt says Read once its session reads it, not Queued for good.
• web: an owner change that meets the card writer's newer revision goes through; one someone else set first is kept.
• setup: automatic checks no longer tick the Zoom app step, and an SDK file in Downloads no longer skips it.
• setup: the Zoom app step waits for "I uploaded the manifest and added the app"; saved credentials alone no longer skip it.
• web: The board inside Zoom no longer says "Open bwat from a meeting" while it works out which meeting it is in; it says that only when bwat's server does.
• web: If Zoom's app kit has not arrived after five seconds, or fails to load, the board inside Zoom says "Zoom is taking a while" and to reopen bwat if it stays. If the kit arrives later, it goes back to "Loading…" until bwat has checked.
• web: The meeting name at the top of the board inside Zoom says "Loading…" until bwat knows which meeting it is in, instead of showing the previous meeting's name for a moment, also when bwat could not check Zoom's sign-in on opening.