Unclaimed Board. Not affiliated with quackbackio. Unclaimed board built from public GitHub data.
Claim Board

Changelog

FeedbackRoadmapChangelogFAQs
Sign in
Powered by Gitback.us
November 6, 2026
v0.15.0

v0.15.0

Quackback 0.15.0 lets you search your whole workspace from Ctrl+K, adds filters to the portal feed, and gives new teams a guided onboarding. Self-hosted installs can now be set up without a browser, and settings can be changed over the API and MCP. API keys now come in two kinds: personal keys that act as the teammate who made them, and workspace keys for integrations. This also tightens how existing keys and sign-ups work, so please read Before you upgrade first.

Before you upgrade

Action needed

  • Replace API keys created by former teammates. Every existing key becomes a personal key: it has the access of the person who created it, checked on every request. If that person has been removed, has left or is blocked, the key stops working and returns 401. Removing a teammate also revokes their personal keys, and adding them back doesn't restore them. For integrations that must outlive any one person, create a workspace key in Settings > Developers. (#728, #904, #905)
  • Check keys made by teammates who can't see every conversation. A personal key now sees only the tickets and conversations its creator can see, over REST and MCP, including when it opens one by its ID. Keys made by Owners, Admins, Managers and Support leads see no change. A key made by someone limited to their own or their team's items now gets only those, and 404 for the rest. (#904)
  • Re-send pending invitations after upgrading. Invitation and account recovery links sent before the upgrade show "invalid link" afterwards, because the sign-in library now stores them differently. (#772, #774)
  • Set your proxy headers if you run behind a reverse proxy. Anonymous posting is now limited to 5 posts per IP address per hour. Without TRUSTED_PROXY_HOPS or TRUSTED_CLIENT_IP_HEADER, Quackback sees every visitor as the proxy's address, so they all share one limit. (#706)
  • Allow a longer first start on large databases. New search indexes are built before the server starts, so raise health check and deploy timeouts if your database is large. (#779, #901)

Behaviour changes

  • Personal keys can't exceed their creator's role. A key made by an admin who is now a member has member access. (#728)
  • MCP tools check permissions one by one. People on custom roles, and the keys and apps they use, may lose tools their role doesn't cover. (#728)
  • Keys with the write:settings scope can now change workspace settings. Check which keys hold it. (#740, #841)
  • The AI agent hands over when it needs a teammate to confirm an action. If it wants to use a tool you've set to "ask first", the customer sees "Connecting you to the team" and the conversation is routed to your team. The assistant.handed_off webhook fires with the reason awaiting_confirmation. (#898)
  • Stricter API validation. A comment reaction must be a single emoji, and a status incident must use its own statuses and services that exist. Anything else returns 400. (#731, #715)
  • The audit log CSV has six new columns. channel, credential_kind, credential_id, client_name, on_behalf_of_principal_id and on_behalf_of come after the existing ones, so scripts that read the first columns by position keep working; check any that read the row as a whole. (#733)
  • Status page RSS items have new IDs. Feed readers will show past updates as new once. (#714)
  • The Copilot on Home Labs experiment is gone. Home shows the overview again. Teammates use Copilot from the conversation and ticket panel and in Slack. The experiment was off by default. (#900)
  • 17 database migrations run on start. They correct the start times of past maintenance windows, split the AI permission in two, and mark every existing API key as a personal key. Every role that had the AI permission gets both halves, so nobody gains or loses access. (#738, #905)

What's new

Search and the portal

  • Search everything from Ctrl+K. Posts, conversations, tickets, help center articles, changelog entries, people, teammates and companies appear in one ranked list, showing only what you can open. Press Enter for a full results page with type filters and highlighted excerpts. With an embedding provider set up, it also finds matches by meaning. (#901)
  • Smarter search in the portal, widget and feedback list. Search matches the start of words, tolerates typos, and falls back to close matches when nothing matches exactly. A new Best match sort puts the closest results first, and a search with no results can be posted as a new post. (#778, #779, #780)
  • Portal feed filters. Filter the feed by status, board, tag and view, and click a filter's chip to change it. Shipped posts link to the changelog entry that announced them, and the header stays visible as you scroll. (#777, #807, #808)
  • Author-only replies. A board can limit replies to the post's author and your team. Contributed by @shamblashini. (#433)
  • Title-only posts. Posts no longer need a description. (#701)

API keys

  • Your own API keys. Every teammate can create, rename, rotate and revoke their own personal keys in their account settings, under API keys. New keys expire after 90 days by default. Admins can turn off new personal keys. (#906)
  • Workspace keys for integrations. A workspace key has its own role, picked when you create it, and keeps working when people leave. Create one in Settings > Developers. You can only give a key a role whose permissions you hold, and only an admin can give one the Owner role. Admins see every teammate's personal keys there and can revoke any of them. (#905, #906)

Onboarding and admin

  • Guided onboarding. New workspaces get a setup wizard, a launch plan on Home, a product tour, a Messenger preview, and quick ways to install Messenger and invite the team. Welcome and setup emails arrive in the team's language. (#706)
  • Your logo, offered from your website. New workspaces look up the company website and offer the logo it finds. It is never applied without asking. Turn the lookup off with DISABLE_AUTOMATIC_BRANDING=true. (#706, #723)
  • Support lead role. A new built-in role for running support. AI settings now have two permissions: Customer-facing AI and Teammate AI. (#738)
  • See where each change came from. Every audit log entry shows whether a change came from the app, the API, MCP, the AI, a workflow or the system, and which key or app made it. (#733)
  • Simpler custom sending domains. Setup takes three DNS records. Quackback checks them automatically for 72 hours and tells you when the domain goes live or breaks. A new Settings > Domains page shows all your domains, and a verified sending domain also verifies SSO domains under it. (#887, #894)
  • Quinn is now Quackback AI. The built-in AI agent has a new name. (#711, #789)

Languages

  • Thai and Ukrainian. Contributed by @iPLAYCAFE-dev and @shamblashini. (#692, #720)
  • Every language fully translated. Polish terms were updated by @ggfunnn, and browsers set to plain pt now get Brazilian Portuguese. (#638, #707)

API, MCP and integrations

  • Workspace settings over REST and MCP. Read and change settings with /api/v1/settings or the get_settings and update_settings tools. Every change returns a receipt you can undo, and ?dry_run previews a change without saving it. (#740, #841)
  • Sign in from CLIs and MCP clients. Tools without a browser can sign in by entering a code on the new /device page. (#739)
  • New webhook events. post.mentioned, post.owner_assigned, and status page events for incidents, maintenance and component changes. (#727)
  • Complete API reference. The OpenAPI spec now covers every public route, and /api/v1/members works again. (#725)
  • Tracking consent in the widget. Hold visitor tracking until consent with init({ tracking: false }), then call Quackback.tracking(true). Page-view counting and the device id can also be switched off per workspace. Both stay on by default. (#782, #785)

Self-hosting

  • Set up without a browser. POST /api/v1/setup with a SETUP_TOKEN creates the workspace and first admin. If you don't set a token, the server prints one to its log on first start. The endpoint switches off once an admin exists. (#739)
  • Setup is locked to the first account. On a new install, nobody else can sign up until setup is finished. To hand an unfinished setup to someone else, set SETUP_OWNER_EMAIL and restart. (#702)
  • Session replay masking options. If you use PostHog, POSTHOG_SESSION_RECORDING_MASK_TEXT and POSTHOG_SESSION_RECORDING_MASK_INPUTS control what replays hide. Both stay on by default. (#800)
  • A one-time GitHub star prompt. After a few weeks of use, each teammate is asked once to star Quackback on GitHub. Turn it off with DISABLE_GITHUB_STAR_PROMPT=true. (#896)

Security

  • Votes stay private. Nobody can list the posts another person voted on. (#705)
  • Restricted changelog entries stay out of RSS. The changelog feed respects category restrictions. Contributed by @kytenz. (#801)
  • No comments on merged posts. A post merged into another can no longer receive comments. (#713)
  • API keys stay inside their creator's access. A personal key can no longer list, open or change tickets and conversations its creator can't see. (#904)
  • MCP get_ticket checks access. It returns only tickets the caller can see. Contributed by @melihsunbul. (#750)
  • Changelog links follow who can see the changelog. Posts no longer link to a changelog that is closed to the person viewing them. (#902)
  • MCP flags customer-written text. Tool results mark text written by customers, so AI clients don't follow instructions hidden inside it. (#730)
  • Dependency patches. Fixes for GHSA-qx66-fv34-fjm8 and GHSA-27r3-jxmh-p828, and the sign-in library's magic link fix. (#771, #772, #829)

Bug fixes

  • Status page. People who unsubscribed are no longer added back, and emails only cover the services each subscriber chose. Rescheduled maintenance no longer starts at the old time, and no status update is lost if the server stops mid-change. (#714, #715, #722, #736)
  • Jira. Status sync no longer stops silently after about 30 days. (#788)
  • Domains. A slow DNS lookup no longer marks a working sending or help center domain as broken. (#890)
  • Discord. The channel picker shows which channels the bot can post in, and explains why adding one failed. (#835)
  • Help center SEO. Article titles include the workspace name, sitemap links use https, pages have canonical links, and repeated headings get their own anchors. (#783, #787)
  • Inbox. The team response count is correct again, and searching status incidents works. (#828)
  • Moderation. Approve and reject say when they fail, and rejected posts no longer show the review banner. Contributed by @Nuenni. (#893)
  • Portal filters. Fixed a rendering issue when changing feed filters. Contributed by @MisakaMirai. (#876)
  • Accessibility. Focus rings are clearly visible, touch targets are larger, admin pages have their own tab titles, and long workspace names fit the portal header. (#698, #700, #699)
  • Performance. English pages are smaller to download, and the inbox and settings respond faster. (#716, #719, #721, #830)
  • Long dialogs. Dialogs and side panels stay inside the screen and scroll, instead of running off the top and bottom. (#907)
  • Wording. Board items are called posts everywhere. (#895)

Contributors

Thank you to the community contributors in this release:

  • @iPLAYCAFE-dev added Thai. (#692)
  • @shamblashini added Ukrainian and author-only replies for boards. (#720, #433)
  • @ggfunnn translated the remaining portal text and updated the Polish terms. (#638)
  • @kytenz kept restricted changelog entries out of the RSS feed. (#801)
  • @Nuenni made moderation errors visible. (#893)
  • @MisakaMirai fixed a rendering issue in the portal filters. (#876)
  • @melihsunbul made MCP get_ticket check the caller's access. (#750)
  • @theluckystrike co-wrote the widget hand-off tests. (#691)

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.14.1...v0.15.0

Shipped from your feedback

  • Admin post modal keeps showing Approve/Reject after a post was rejected, further clicks fail silently0 votes
  • Widget → portal hand-off fails for any visitor that already has a cookie on the portal host (403 MISSING_OR_NULL_ORIGIN)0 votes
October 7, 2026
v0.14.1

v0.14.1

A patch release for 0.14.0. It fixes opening the portal from the widget for returning visitors, Microsoft sign-in with a Tenant ID, "Load more" on the public changelog and unsubscribe links opened by email scanners. It also gives identity providers a clearer Profile and Roles setup, lets you add people who already sign in as teammates, and patches three dependency advisories.

Upgrade the same way as any patch: pull the new image and restart.

Upgrading

  • One new database migration - Adds a table that records the name and avatar each identity provider last wrote. It runs automatically on start and changes no existing data.
  • New optional setting - EMAIL_SES_MAX_SEND_RATE caps Amazon SES sends per second for each Quackback process (default 10). If several processes share one SES account, set it to roughly the account's per-second quota divided by the number of processes.

Security

  • Dependency advisories patched - Updated proxy-addr (IP spoofing through an IPv4-mapped IPv6 trusted subnet), source-map-js (denial of service) and the MCP TypeScript SDK (OAuth credentials could be sent to an authorization server chosen by the MCP server).
  • Require SSO covers email sign-in links - The portal's email sign-in now refuses an address at a verified domain that requires SSO, like every other sign-in method.
  • Email changes always confirm the current address - Changing an email goes through the flow that proves the current address first, and accounts at a domain that requires SSO keep the address their provider gave them.
  • Admin-entered emails are not marked verified - Editing a person's email in People clears its verified flag unless the address is unchanged.

Improvements

  • Profile card for identity providers - A provider's page always shows what Quackback takes from it for each person (account ID, email, name, username and avatar), next to the values from the last test sign-in.
  • Avatar and username claims - Choose which claim holds a person's avatar or username when your provider doesn't send the standard ones, with a preview of the picture before you apply it.
  • Keep names and avatars in step with the provider - An optional per-provider setting updates name and avatar on every sign-in, and never overwrites a name or picture someone changed in Quackback.
  • One Roles card - Role rules, the default role and when roles are applied now live in one card on the provider's page. Rules can give custom roles, and a guard blocks a change that would remove admin access from the provider's own admins.
  • Add people who already sign in - One Add people dialog finds people who have signed in and makes them teammates right away, or invites new addresses by email. Only admins can grant the Admin role.
  • One-click unsubscribe - Notification emails carry unsubscribe headers so mail clients can offer one-click unsubscribe. Opening an unsubscribe link now asks for confirmation, so link scanners can no longer unsubscribe people.
  • Paced Amazon SES sending - Large announcements go out at a steady rate instead of running into SES throttling.

Fixes

  • Opening the portal from the widget works for returning visitors - Visitors whose browser already had a cookie on the portal saw "Sign-in link expired" instead of being signed in, which affected almost everyone after their first visit. (#642)
  • Microsoft sign-in uses your Tenant ID again - In 0.14.0 the Tenant ID you configured for Microsoft sign-in was ignored and every sign-in used the "common" endpoint, so single-tenant app registrations could not sign in and sign-in was not limited to your directory. The setting is labelled "Tenant ID" again, and values saved in 0.14.0 are picked up automatically.
  • Default role shown correctly - A provider with no saved default role now shows Member, which is what sign-in gives people at a verified domain.
  • Changelog "Load more" works - Loading more entries on the public changelog failed in the portal and widget once a workspace had more than one page of entries.
  • Changelog feed paths - /changelog/rss and /changelog/rss.xml redirect to the feed, and a malformed entry link shows not found instead of an error.
  • Webhook dialogs scroll - The create and edit webhook dialogs scroll on smaller screens, so the save button is always reachable. (#672)
  • Magic-link hint lists every email provider - The magic-link setting now names Resend alongside SMTP and Amazon SES.
  • Self-hosting guide corrected - Requirements (PostgreSQL 14+ with pgvector 0.5.0+ and pg_trgm), published image tags, migrate and start commands, the Railway deploy link, and connection pooling advice are now accurate.

Internal

  • Quieter error logs - Expected failures such as invalid form input, closed connections, unconfigured integrations, email throttling that will be retried and AI work refused by the AI allowance are logged as warnings or info instead of errors.
  • AI usage accounting - Embedding calls are recorded in the AI usage log without counting toward any allowance, and help center auto-translate pauses while an AI token allowance is used up.

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.14.0...v0.14.1

Shipped from your feedback

  • Bug: Webhooks list has no scroll0 votes
October 5, 2026
v0.14.0

v0.14.0

Quackback 0.14.0 turns the app into a full support platform alongside feedback. There is a shared support inbox with a live messenger, tickets, an AI agent (Quinn) and a teammate Copilot, visual workflows with SLAs, a help center with Ask AI, and public status pages. Admin navigation and styling have been rebuilt around one consistent look, permissions are now granular with custom roles, and the widget, integrations, API and MCP all grew to match. New workspaces start with Feedback and Changelog on. Turn on Support, Help Center and Status in Settings > General (existing workspaces keep what they had).

Upgrading from 0.13? Read Before you upgrade first. It covers the backup, the new database requirements and the configuration changes.

Before you upgrade

0.14 is a large release. Read this section first; the full guide is in the docs under Self-hosting > Upgrading from 0.13 to 0.14.

  • Back up first - Take a database backup (pg_dump) and a copy of your object storage. There is no downgrade path: 0.13 cannot run against the upgraded database, so rolling back means restoring the backup.
  • Stop the old version - Stop the 0.13 container before starting 0.14. Do not run the two side by side.
  • Let the first start finish - The first start runs about 140 database migrations and logs each one. On a large install this can take several minutes. Do not restart the container while it runs; nothing is applied until the whole set succeeds, and search indexes are built afterwards.
  • Database requirements - PostgreSQL 14 or newer with pgvector 0.5.0 or newer and pg_trgm. The bundled images already meet these. If yours doesn't, startup stops before changing anything and says what to fix.
  • Use a direct database connection - DATABASE_URL must be a direct or session-mode connection, not a transaction-mode pooler, because live updates use Postgres LISTEN/NOTIFY. Quackback logs an error if it detects this.
  • Redis is no longer used - Background jobs now run inside Quackback itself. Let pending jobs finish before upgrading, then remove REDIS_URL and the Redis or Dragonfly service and volume.
  • One email provider - Configure exactly one sending provider: SMTP, Amazon SES or Resend. If more than one is set, Quackback will not start and the log names the variables to remove. To keep a Resend key only for receiving email while SMTP or SES sends, set EMAIL_INBOUND_PROVIDER=resend.
  • Reverse proxies - Set TRUSTED_PROXY_HOPS=1 if Quackback runs behind nginx, Caddy, Traefik or a Cloudflare tunnel (2 behind a CDN plus a proxy). Without it, every visitor shares one rate limit, including sign-in attempts, so sign-in can be throttled for everyone on a busy install. Leave it at 0 if clients connect to Quackback directly. If your proxy sets one client-address header itself (for example nginx proxy_set_header X-Real-IP $remote_addr;), set TRUSTED_CLIENT_IP_HEADER=x-real-ip instead.
  • SECRET_KEY is required - The production compose file refuses to start without it. Keep your existing value.
  • Bundled object storage - The production compose file now uses Silo instead of MinIO, which no longer publishes images. Follow the Silo steps in deploy/self-hosted/README.md.

What changes when you upgrade

  • Existing files keep working - Files uploaded before upgrading (avatars, logos, post images, attachments) are copied into the new storage layout automatically in the background on first start, and files uploaded during a rolling upgrade are picked up for a day. Originals are kept, so an earlier backup can still be restored. Links to older chat and widget images keep working, including links in emails that were already sent.
  • Single sign-on keeps working - SSO and custom OIDC providers that existed before 0.14 keep sending their original redirect URI (/api/auth/oauth2/callback/<id>), so no change is needed at your identity provider. New providers use /api/auth/callback/<id>. To move an older provider, add the new URI at your identity provider, then open the provider, choose Edit, select Switch to new URI and test the connection again.
  • Roadmaps follow status - Roadmaps now show posts by status instead of hand-placed lists. Existing placements are kept in a post_roadmaps_archived table for reference and will be removed in a later release.
  • Roles - Admins become Owners and members become Managers. Managers can now also manage portal users, segments, board access and the help center, and export posts. Review your team's roles in Settings.
  • Sign-ups - The "open sign-up" setting now applies to every sign-in method, including Google, GitHub, OIDC and magic links.
  • Help center and messenger - A help center or messenger you had switched off stays hidden after upgrading. Turn them on in Settings when you are ready.
  • AI spam filter - The new AI spam filter is off on upgraded installs. Turn it on in Settings > Channels > Email.
  • Widget identify - identify now requires a signed ssoToken; unsigned { id, email } calls leave the visitor anonymous. Inline email capture in the widget was removed.
  • API - IDs from earlier releases are still accepted, but responses use the new prefixes (for example post_status_, post_comment_, conversation_msg_). isPublic on roadmaps is accepted as a deprecated alias for visibility. Conversation status pending is now snoozed.
  • Slack - The Slack app's request URLs changed to /api/integrations/slack/hooks/... and installs need to be re-authorised.
  • Importers - The command-line import scripts for other feedback tools were removed. Import with CSV from Settings > Imports.
  • AI feedback extraction - The experimental AI feedback extraction feature and its Slack channel monitors were removed, along with their data.
  • Custom SQL - Some tables were renamed (for example votes to post_votes and comments to post_comments). Update any reports or scripts that query the database directly.
  • Theme - Portals use the new single theme. Check any custom CSS.
  • Email footer - Outgoing emails include a small "Powered by Quackback" footer.
  • Telemetry - The anonymous daily usage ping now includes more banded counts and is sent to PostHog. Every field is listed in docs/telemetry.md. Opt out with DISABLE_TELEMETRY=true.
  • AI providers - Summaries, duplicate detection, sentiment and auto-tagging work with OpenAI-compatible servers that don't support JSON schema output.
  • Sign-in rate limits - Sign-in limits now use the same client address as the rest of Quackback, so one client can no longer lock everyone out and a forged X-Forwarded-For header no longer bypasses the limit.
  • Sessions - Some users will need to sign in again.

What's new

Support inbox and messenger

  • Unified support inbox - Conversations and tickets live in one list and thread with shared views, filters, a details panel and keyboard shortcuts. Turn it on in Settings > General.
  • Messenger in the widget - Visitors chat with your team from the widget, with unread badges, a proactive greeting bubble, and a note when the team is back.
  • Group threads - Add a second customer to a conversation so everyone receives every reply, and remove them again later.
  • Macros everywhere - Open the macro picker with M, or apply a macro from the bulk bar to reply to every selected conversation.
  • Bulk actions and snooze - Tag, change status or reply to many conversations at once, and snooze with natural-language times like "tomorrow morning".
  • Better inbox search - Results rank by relevance and show the matching keyword in context.
  • Spam filtering - Obvious spam is filed to a restorable Spam view, with trusted senders you manage in settings and bulk restore or delete.
  • Conversation data - Custom attributes, managed tags, AI attribute detection and "Created by me" views.
  • People and companies - Company directory and profiles, richer user profiles, duplicate detection with lead merge, admin tags and a Country column.
  • Email channel - Receive and send support email from your own address with verified sending domains, threaded replies, attachments and inline images. Set it up under Settings > Channels.

Tickets

  • Tickets alongside conversations - Durable, trackable requests with custom ticket types, per-type fields, statuses and customer-visible stages. Turn it on in Settings > General.
  • Customer ticket view - Requesters follow their tickets from the widget and portal with stage updates and replies.
  • Watchers and activity - Watch or mute a ticket and see a full activity log of every change.
  • Tracker links - Create or link issues in your tracker from a ticket, and stage changes flow back to every linked customer.
  • Ticket emails - Lifecycle and SLA emails thread properly and accept replies by email.
  • Intake forms in chat - Post a ticket form inside a conversation and collect the request as a card.

Automation and AI

  • Quinn AI agent - Quinn answers customers in the messenger from your knowledge, takes approved actions, and hands off to a person when needed. It needs an AI provider, and you can pause its replies under Settings > Agent.
  • Knowledge sources - Ground Quinn on articles, snippets, uploaded PDFs and Word documents, public URLs and past conversations.
  • Custom actions and connectors - Build step-by-step actions and connect external systems, with approval for sensitive steps.
  • Improve-answer loop - Corrections you make become snippets Quinn can reuse.
  • Copilot for teammates - A sidebar in the inbox drafts answers with cited sources, and Modify lets you shorten, translate or redraft before inserting. You can also save an answer as a macro or summarize a thread.
  • Two-way translation - Read and reply to customers in their own language.
  • Visual workflows - Build automations on a canvas with triggers, conditions (country, locale, plan, keywords, ticket type), customer-facing messages, timers and webhooks, with version history and dry runs.
  • SLAs and office hours - Set response and resolution targets with business hours and holidays, see countdowns in the inbox, and report on attainment.
  • AI tagging - Describe a tag and new posts are tagged automatically, with a one-click backfill for existing posts.
  • Support reports - Conversation volume by channel, first-response and time-to-close trends, per-teammate performance and satisfaction for AI-handled chats.

Help center

  • Ask AI - Visitors get a streamed answer with inline citations, and a graceful reply when nothing matches.
  • Custom domain and indexing - Serve the help center on your own domain with redirect rules and indexing control.
  • Per-article languages - Add article translations, with AI-drafted translations to start from.
  • Audience control - Limit categories or single articles to chosen segments.
  • Article insights - See article performance, search terms with zero-result tracking, and the reasons readers give for unhelpful votes.

Status pages

  • Public status page - Components, incidents, scheduled maintenance, uptime history and subscriber notifications, visible to everyone or limited to segments. Turn it on in Settings > General.
  • Incident tools - A lifecycle stepper for incidents, separate report and schedule dialogs, templates and drag-to-organize services.

Feedback and roadmap

  • Saved views - Save an inbox filter set as a named view, with counts on filter options.
  • Moderation and bulk status - A moderation queue in Feedback, bulk status changes, and priority sorting.
  • Pin posts - Pin a post to the top of its public board.
  • Board custom fields - Collect extra answers on the public submission form.
  • Video uploads - Attach native videos to feedback.
  • Roadmap views - Configurable roadmap views, comment counts on cards, and smoother drag and drop.

Changelog

  • Categories and subscribers - Organize entries into categories and send publish emails to subscribers, with a segment picker for targeted announcements.
  • Richer entries - Featured hero images, full formatted email bodies, and a top-viewed table.

Admin and permissions

  • Custom roles - Create roles from granular permissions and assign them to members, invites and API keys.
  • One consistent admin - A new two-tone theme, Home in the rail, one toolbar across work areas and flat Settings navigation.
  • Notifications - Per-type, per-channel preferences, archive and filter, and links that jump to the right place.
  • Onboarding - A goal-based start with a launch checklist.
  • Visitor analytics - Pageview and visitor reports with no cookies, from portal and widget traffic.

Sign-in and SSO

  • Simpler OIDC setup - Connect, test and enable, with scopes you can edit and a clear view of the claims your provider returns.
  • Providers without email - Sign in works when an identity provider withholds an address, and people are asked for a contact address.
  • Account linking - Guided email confirmation recovers sign-ins that could not be linked.

Integrations

  • Two-way status sync - Linked issues and statuses stay in step, with search across linked items.
  • GitLab self-hosted - Point issue sync at your own GitLab instance.
  • GitHub issues as conversations - Inbound GitHub issues sync and can be linked from the admin.
  • Slack and webhooks - More events, including votes, ticket replies and notes, and retries that continue for about seven hours.

API and MCP

  • Writable REST for support - Create and update tickets, conversations and moderation through the v1 API.
  • More endpoints - Companies (with filters and member counts) and post voters.
  • Ticket tools in MCP - Create, reply, note and link tickets from your AI client.
  • Scoped OAuth - MCP clients get least-privilege scopes, and write access implies read.

Widget

  • Home tab - Cards for recent tickets and changelog, per-audience cards and a hero backdrop with patterns and colors.
  • Launcher controls - Choose its position and label, and badge it for unread messages and updates.
  • Easier install - A two-step install that keeps your signing secret out of chat.

Localization

  • New languages - Dutch and Polish join the interface languages.
  • Local dates - Dates and relative times follow the app's language.
  • Translate customer-facing text - Edit widget copy per language in admin.

Self-hosting

  • Simpler stack - Background jobs run inside Quackback on Postgres, so Redis is no longer needed, and the bundled object storage is Silo.
  • Scale out with roles - Run separate web and worker containers with QUACKBACK_ROLE.
  • Safer upgrades - Startup checks database requirements before migrating, logs each migration, and rebuilds interrupted search indexes.
  • Data export and import - Workspace ZIP export and a mapping wizard with dry runs for imports from other tools.
  • Faster pages - Fewer requests and queries across the app.

Shipped from your feedback

  • Proposal & roadmap: contributing ticketing, CRM, RBAC, SLA & content-visibility as a reviewable 10-PR stack3 votes
  • [Bug] Merge assessment always fails with 400 against OpenAI: z.record renders propertyNames, which Structured Outputs reject0 votes
  • [CI] Restore dependency-audit gate on next (7 unallowlisted high advisories)0 votes
  • [DB] Reconcile next migrations with Drizzle schema (11-statement drift)0 votes
  • [Feature] Add an authorization regression matrix for admin, member, user, anonymous, widget, API-key, and MCP access0 votes
  • [Feature] Add rich readiness checks and an admin operations dashboard0 votes
  • [Feature] Convert CSV imports into async jobs with dry-run preview, progress, cancel, and rollback support0 votes
  • [Feature] Custom Gitlab Urls0 votes
  • [High][Security] Bound inbound webhook body reads before signature verification0 votes
  • [High][Security] Enforce granular API-key scopes across REST and MCP0 votes
  • [High][Security] Reduce OAuth dynamic-client default scopes and disclose offline access on consent0 votes
  • [High][Security] Split public and private storage access instead of exposing every known S3 key0 votes
  • 2FA sign-in fails: better-auth 1.6.30 lockout writes columns two_factor doesn't declare0 votes
  • Bug: Webhooks and workflows are not firing on main0 votes
  • Feature Request: Limit changelogs to certain segments0 votes
  • New deployment fails with Redis config validation error0 votes
  • QUACKBACK_WIDGET_SECRET No mechanism exists to acquire this0 votes
  • Self Hosted GitLab for two-way synchronization of issues and statuses0 votes
  • Self-hosting: docker-compose.prod.yml pulls minio/minio and minio/mc from Docker Hub, which denies anonymous pulls0 votes
  • Widget post composer uploads an image before any session exists, so attaching 401s for a first-time visitor0 votes
August 1, 2026
v0.13.2

v0.13.2

This release adds Slack notifications for support conversations and visitor messages, fixes inbound chat email replies with Resend's metadata-only webhooks, keeps images in posts that contain emoji, self-hosts all branding fonts (no more Google Fonts <link>), and makes OIDC sign-in work with providers that don't support select_account. It also makes sentiment analysis tolerant of models that wrap JSON in code fences.

Features

  • Slack notifications for support chat. Slack targets can now notify when a visitor starts a support conversation (conversation.created) and when a visitor sends a message (message.created), each with a deep-link into the admin inbox. Agent replies never notify, and both events are opt-in per target in Settings → Integrations → Slack. (#335)

Bug fixes

  • Inbound chat email replies deliver with Resend. Resend's email.received webhook is metadata-only, so replies arrived without a body and were dropped. The body is now fetched from the Received Emails API after routing and dedupe (with an HTML→text fallback), and a transient fetch failure retries via Resend redelivery. (#325, fixes #320)
  • Images kept in posts that contain emoji. A post written with the : emoji picker made the whole document non-reserializable, so API output fell back to stored markdown and lost embedded images. Emoji nodes now serialize to their Unicode character (or :name: for custom emoji), and images survive. (#338)
  • Self-hosted branding fonts. Every font in the branding picker and theme presets is now bundled via @fontsource instead of loaded through a Google Fonts <link>, which edge optimizers (e.g. Cloudflare Fonts) rewrote into inline @font-face and broke SSR hydration. Saved "Geist" configs automatically map to the bundled "Geist Sans" family. (#321)
  • OIDC sign-in works with more identity providers. Generic OAuth/OIDC sign-in now requests prompt=login instead of the OIDC-optional select_account, which many IdPs ignore or reject. Re-authentication is still forced, so an admin typing a specific email isn't silently signed in as an existing IdP session. (#347)
  • Sentiment analysis tolerates fenced JSON. Models that wrap their JSON response in markdown code fences no longer break sentiment parsing. (#315, closes #296)

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.13.1...v0.13.2

June 29, 2026
v0.13.1

v0.13.1

This release fixes dark-mode theme flashing and its cache keying, repairs slug generation for non-Latin and symbol-only board and help-center names, makes inbound chat email replies deliver reliably, restores images in API/MCP/webhook content, and splits the CSAT webhook so integrations stop double-counting ratings. It also adds a presentation-only published-date override for changelog entries.

Features

  • Changelog published-date override. Set or clear a presentation-only published date on a live changelog entry, separate from when it actually went live. The portal list, detail, feed, and sitemap all use the chosen date, and it never sends notifications. (#288)

Bug fixes

  • No more white flash in dark mode. The server now commits the resolved theme straight onto the rendered page, so dark-mode visitors no longer see a white flash on load. The system setting is resolved server-side too on browsers that report the OS preference, and the response is cache-keyed correctly so a shared cache can't serve a mismatched theme. (#297, #298)
  • Images preserved in API, MCP, and webhook content. Rich-text posts, changelog entries, and help-center articles dropped embedded images from the markdown returned by the REST API and MCP and emitted in webhook and notification payloads. Markdown is now rendered from the source rich text so images survive as ![alt](src), and existing entries self-heal without a backfill. (#317, fixes #292)
  • Valid slugs for non-Latin and symbol-only names. Board and help-center names in scripts like Chinese, Japanese, or Korean (or emoji- and punctuation-only names) no longer produce an empty slug that broke board selection and help-center routing. Names are transliterated to a readable slug, with a safe fallback when nothing remains, and existing broken slugs are healed. (#295, closes #285)
  • Inbound chat email replies deliver again. Agent reply-to addresses exceeded the 64-character local-part limit some providers enforce, so inbound replies were rejected and never reached the visitor. The address now stays within the limit. (#294, fixes #293)
  • CSAT webhook no longer double-counts. A satisfaction survey now emits conversation.csat_submitted exactly once when the rating is banked, and an optional follow-up comment rides its own conversation.csat_comment_added event, so integrations stop double-counting a rating when a visitor adds a comment. (#299)
  • Reliable changelog publish notifications. Publish notifications now fire exactly once per entry and recover automatically if the delivery job is dropped, so subscribers are never missed or notified twice.

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.13.0...v0.13.1

June 27, 2026
v0.13.0

v0.13.0

This release unifies sign-in into a single dialog for both portal users and team admins, and reworks SSO into a multi-provider model: you can register any number of OIDC identity providers, each with its own verified domains, email routing, and per-domain enforcement. It also ships a redesigned provider editor, a settings-permission fix, and a security update.

Upgrade notes for self-hosters

  • Auth and feature flags are now managed in the admin UI only. The config file no longer applies auth or features blocks. If yours still contains them they are ignored (and surfaced as a warning in status), not a hard error. Configure sign-in methods, OIDC providers, and feature flags under Settings.
  • Magic link is opt-in. Magic-link sign-in is now off by default for every role unless enabled. Upgrading workspaces keep whatever sign-in methods they already had working.
  • Old auth routes redirect. /admin/login, /auth/login, /auth/signup, /sso, and the standalone two-factor pages now redirect into the unified sign-in dialog.

Features

  • One sign-in surface for everyone. Portal users and team admins now sign in through the same dialog, with a recovery-code break-glass path for SSO-only workspaces. (#284)
  • Multiple OIDC identity providers. Register any number of OIDC providers (Okta, Microsoft Entra, Google Workspace, Auth0, Keycloak, or any OIDC issuer). Each provider carries its own verified domains: emails at a verified domain are routed to that provider, and a domain can be enforced so its users sign in with SSO only. Roles map from the provider's group or role claims, and a claim-attested role provisions regardless of email domain. (#284)
  • Redesigned SSO provider editor. One default-role control, progressive group/claim mapping with autocomplete, full ID-token inspection in the connection test, manual-endpoint support for IdPs without a discovery document, and a per-provider toggle to show or hide the sign-in button. (#287)
  • Inline two-factor. Two-factor enrollment and challenge now happen inside the sign-in dialog instead of separate pages. (#284)

Bug fixes

  • Settings are admin-only. The settings cog is hidden from non-admin team members, and a non-admin who reaches an admin-only page sees a calm permission notice instead of a raw error. (71b6c8f6)

Security

  • nodemailer 9.0.1 (GHSA-p6gq-j5cr-w38f). Patches a message-level option that could bypass file and URL access controls. Quackback never used the affected option, but the dependency itself was flagged. (74d3dab4)

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.12.4...v0.13.0

June 19, 2026
v0.12.4

v0.12.4

This patch lets portal users at a verified domain sign in with SSO, and quiets health-check noise in self-hosted logs.

Features

  • Portal SSO sign-in. Portal users at a verified domain can now sign in with SSO instead of being offered it and then rejected at the callback. (#264)

Internal

  • Quieter health-check logs. Successful health-check requests are no longer written to the access log, cutting recurring probe noise; failed probes and errors are still recorded. (#257)
  • Workspace state cleanup. Removed unused internal workspace state-handling code. (#267)

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.12.3...v0.12.4

June 15, 2026
v0.12.3

v0.12.3

This release adds Simplified and Traditional Chinese, an ntfy integration, and structured logging for self-hosters, plus fixes to private-portal sign-in and outbound automation delivery.

Features

  • Simplified and Traditional Chinese. The portal and widget are now available in zh-CN and zh-TW, served automatically based on browser language. (#244)
  • ntfy notifications. Send notifications to your own devices through the new ntfy integration. (#242)
  • Language-aware page rendering. Pages now declare their language and text direction during server rendering, so right-to-left locales display correctly from the first paint. (#246)
  • Structured server logs. Self-hosted deployments now emit structured JSON logs for easier searching and monitoring. (#245)

Bug fixes

  • Private portal sign-in. Signing in to a private portal now lands you in cleanly: no flash of the logged-out buttons, no crash on the sign-in screen, and no getting stranded on the access wall after authenticating. (#249, #250, #252)
  • Automation delivery. Events now reach n8n, Make, Zapier, and Monday; a channel-resolution mismatch had been silently dropping every event. (#241)

Internal

  • Widget locale parity. The widget and app now share a single supported-locale list, so they can't drift apart. (#248)
  • Route tree cleanup. Colocated route-helper modules are excluded from the generated route tree, silencing dev-server warnings. (#251)

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.12.2...v0.12.3

June 15, 2026
v0.12.2

v0.12.2

A small follow-up to v0.12.1 with one fix that landed just after it was tagged.

Bug fixes

  • Custom OIDC setup shows the correct callback URL. The "Configure Custom OIDC" modal listed /api/auth/callback/<id>, but better-auth's genericOAuth callback is /api/auth/oauth2/callback/<id>, so registering the shown value at the IdP failed with a callback mismatch. The modal now shows the correct path; built-in social providers (Google, GitHub) are unchanged. (#238, closes #233)

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.12.1...v0.12.2

June 15, 2026
v0.12.1

v0.12.1

This patch fixes sign-in on 0.12.0 (the admin dashboard was unreachable behind a React Intl error), restores OAuth-only portal sign-in, and hardens auth, SSO, and file uploads.

Bug fixes

  • Admin sign-in works again on 0.12.0. Signing in at /admin/login dead-ended on a blank "[React Intl] Could not find required intl object" page, leaving the dashboard unreachable; the form now renders. (#234)
  • Portal sign-in with only OAuth/OIDC enabled. With password and magic-link off and just an OAuth provider (a custom OIDC provider or Discord), the portal showed a dead-end email field; it now shows only the provider button. (#235, closes #231, #186)
  • Settings toggles persist after saving. Some toggles reverted on the next view because the query cache wasn't invalidated after a save. (#230)
  • Admin avatar loads with the page. The sidebar avatar now server-renders and is fetched during the initial load instead of after hydration. (#236)
  • Invitation links are revocable and last 30 days. (#228)

Security

  • better-auth upgraded to 1.6.16. Fixes a refresh-token rotation issue that could force a re-login about once a day, plus a grace window that heals benignly-stale tokens. (#217)
  • PKCE on SSO sign-in. The SSO authorization-code flow now sends PKCE (S256). (#214)
  • Stricter file uploads. Uploaded bytes are verified against the declared image type, proxied reads send nosniff, and trusted-attachment URL matching is tightened to a path-segment boundary. (#219, #218)

Preview, behind Labs (off by default)

This release also lands an early preview of the Support Inbox (agent conversations, a portal Support tab, widget live chat) and inline link previews. They're off by default; enable them under Settings → Labs to try them.

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.12.0...v0.12.1

June 9, 2026
v0.12.0

v0.12.0

This release makes AI configuration explicit (a breaking change if you use AI), promotes Analytics out of Labs, and fixes Shortcut status sync.

Breaking change: AI now requires explicit configuration

AI features are off until fully configured. Previously, Quackback assumed OpenAI's endpoint while hardcoding gateway-style model names, so a self-hoster with just an API key got an error on every AI call (#180).

To enable AI, set all four variables:

OPENAI_API_KEY=sk-...

# Any OpenAI-compatible endpoint, declared explicitly. Examples:
#   Direct OpenAI:         https://api.openai.com/v1
#   OpenRouter:            https://openrouter.ai/api/v1
#   Cloudflare AI Gateway: https://gateway.ai.cloudflare.com/v1/<account>/<gateway>/openai
OPENAI_BASE_URL=https://api.openai.com/v1

# Model ids your endpoint accepts (direct OpenAI examples shown)
AI_CHAT_MODEL=gpt-4o-mini                  # summaries, sentiment, triage, duplicate checks
AI_EMBEDDING_MODEL=text-embedding-3-small  # duplicate detection, semantic search

Upgrading from v0.11.0 or earlier: if you had OPENAI_API_KEY set, add OPENAI_BASE_URL and the two model variables to keep AI working. Until you do, AI features stay off and a warning is logged at startup.

Each feature can also use its own model via AI_SUMMARY_MODEL, AI_SENTIMENT_MODEL, AI_EXTRACTION_MODEL, AI_QUALITY_GATE_MODEL, AI_INTERPRETATION_MODEL, and AI_MERGE_MODEL. Set one to off to disable just that feature. See .env.example for the full reference.

Features

  • Analytics is now generally available. The dashboard is out of Labs and on for every workspace, with period-over-period trends on each metric, a clearer activity chart, and full mobile and tablet support. (#198)
  • Integration credentials from the environment. OAuth app credentials for integrations can be supplied via INTEGRATION_<PROVIDER>_* environment variables by setting PLATFORM_CREDENTIALS_SOURCE=env. The default (database, managed in the admin UI) is unchanged. (#209)

Bug fixes

  • Shortcut status sync now works. Moving a linked story to a new workflow state updates the feedback post's status; previously the webhook arrived but the status never changed. (#204)
  • Webhook signing secret shown in settings. Shortcut and Azure DevOps now display the signing secret needed to finish manual webhook setup, next to the webhook URL. (#204)
  • Complete translations. Portal sign-in screens are now translated, and every locale was backfilled to full parity with English. (#202, #203)

Full Changelog: https://github.com/QuackbackIO/quackback/compare/v0.11.0...v0.12.0

June 4, 2026
v0.11.0

v0.11.0

This release adds a major new opt-in feature, Conversations, alongside a wave of improvements to access, moderation, and the everyday admin experience.

Conversations (new, experimental). You can now switch on real-time chat and a shared support inbox. Visitors message your team right from the widget and see when you're typing and when you've read their message, while your team handles every thread in one place, with assignment, priorities, labels, internal notes, and search. You can reply by email and keep it in the same thread, turn a conversation into a feedback post, and ask visitors how the chat went. It's off by default, so nothing changes until you turn it on.

Granular board access. Every board now controls who can view, vote, comment, and submit, independently. Open each to anyone, to signed-in users, to specific customer segments, or to your team only. So you can let everyone read a board but require sign-in to vote, or reserve submissions for a beta group. New Public and Private presets make setup quick, and your existing boards carry over exactly as they were.

Private portals. Make your feedback portal private with a single switch, then choose who gets in: your team, people on a trusted email domain, anyone you invite, a customer segment, or visitors who signed in through your widget. Private portals show a clean sign-in wall and stay out of search engines. Public portals are unaffected.

Moderation. Optionally hold posts and comments for review before they go public, with a queue to approve or reject. Set it per board or across your whole workspace. Off by default.

Nicer to use, everywhere. Brazilian Portuguese for the portal and widget, new ways to group customers into segments, a friendlier widget home screen with a peek at your latest changelog, a polish pass across the whole admin panel, and reactions that now show who reacted.

For self-hosters. A proper production Docker setup, an image that runs natively on both Intel and ARM machines, smoother running across multiple instances, and a batch of reliability and security fixes.


Features

  • Conversations (new, experimental, off by default). A real-time chat channel in the widget plus a shared agent inbox. Visitors message your team and see typing indicators and read receipts; agents triage from one place with assignment, priority, status, labels, internal notes with @-mentions, message reactions, saved-for-later, and search. Turn it on from the Labs settings.
  • Email replies for conversations. Agents can reply by email and the visitor's response threads back into the same conversation. Requires configuring an inbound email address.
  • Convert a conversation into feedback. Turn a support chat into a feedback post, or upvote a similar existing post on the visitor's behalf, in one step.
  • Customer satisfaction (CSAT). Visitors can rate a closed chat, rolled up in a new Support section of Analytics.
  • Granular board access. A per-board permission matrix controlling view, vote, comment, and submit independently, each open to anyone, signed-in users, specific segments, or team only, with Public and Private presets. (#191)
  • Private portals. Require sign-in to view the portal, with access granted by team membership, trusted email domains, email invites, customer segments, or widget sign-in. Private portals are excluded from search engines and feeds.
  • Post and comment moderation. Optionally hold submissions for review before they publish, configurable per board or workspace-wide and separately for anonymous and signed-in authors, with an approve and reject queue.
  • Brazilian Portuguese. The portal and widget are now available in pt-BR, served automatically based on browser language. Contributed by @arthurbarret0. (#194)
  • More customer segments. Group people by country, language, last-active recency, and signup source.
  • Widget home screen. A new landing tab that greets visitors, points them to the right section, and previews your latest changelog entry, with help articles and messaging combined under one Help surface.
  • Reactions show who reacted. Hover a reaction on a comment or chat message to see who is behind it.
  • Reworked authentication settings. Sign-in providers are managed from one place with a single toggle each, custom identity providers offer a preset picker with issuer auto-detection, and guardrails stop you from locking yourself out.
  • Richer audit log. Each event now records the request ID, actor type, and sign-in method, all included in the CSV export.
  • Multi-architecture Docker image. Official images now run natively on both Intel and ARM. (#195)

Bug fixes

  • Widget hydration error behind font-proxying CDNs. Self-hosting the Inter font stops CDNs that rewrite font links from breaking the widget. (#133)
  • Clearer sign-in rate-limit message. Hitting the sign-in limit now returns a proper "too many attempts" message with a retry hint instead of a misleading "invalid email or password" error.

Performance

  • Faster public changelog. Visibility checks are pushed into the database query instead of loading every linked post and filtering in memory.

Security

  • SSRF hardening for image rehosting. External image fetches now connect to the already-validated address instead of re-resolving DNS, closing a rebinding window reachable across posts, changelog, and help-center content.
  • Integration webhook allowlist. Outbound integration webhooks route through the safe-fetch guard and enforce host allowlists. Thanks to @endscene665.
  • Signed email reply addresses. Conversation reply addresses are cryptographically tied to their conversation, so an agent email cannot be used to inject a reply into someone else's thread.
  • Verified-email guards on portal access. Email-based access grants require a verified email, so a segment rule cannot be used to walk into a private portal unverified.
  • Email masking in logs. Email addresses are obfuscated in unstructured server log output.

Internal

  • Multi-replica-safe background jobs. Background sweepers (audit-log prune, invite expiry, stuck-item recovery, AI summaries, duplicate detection) now run under a cross-instance lock so only one replica runs each tick.
  • Duplicate-detection circuit breaker. The merge-suggestion sweep aborts after repeated failures instead of retrying in place.
  • Hardened production Docker stack. A new docker-compose.prod.yml ships the app and datastores with no exposed database ports, required-secret checks, healthcheck-gated startup, and a private upload bucket; the root docker-compose.yml is now development-only. (#195)

Tests

  • Extensive new coverage across live chat and the support inbox, board and portal access policy, moderation, and email-channel signature verification.

Upgrade notes

  • Run database migrations on upgrade (0066 through 0104). All are additive or migrate existing data automatically; no manual data changes are required.
  • Conversations is experimental and off by default. Enable it from the Labs settings. Inbound email replies additionally require the EMAIL_INBOUND_DOMAIN and EMAIL_INBOUND_SIGNING_SECRET environment variables.
  • Some admin settings pages moved: API is now Developers, User Attributes and Segments are now People, and Portal auth now lives under Security. Update any bookmarks.
  • The legacy board "audience" field was replaced by the new access model. Existing boards are migrated automatically; the REST API still exposes a read-only audience field, and vote endpoints now enforce each board's vote permission (a board that requires sign-in to vote will reject anonymous API votes).
  • Self-hosters: use docker-compose.prod.yml for production (the root compose is now development-only), and note that values in .env files must be unquoted for Docker --env-file.

Contributors

Thank you to the community contributors in this release:

  • @arthurbarret0 added the Brazilian Portuguese (pt-BR) translation. (#194)
  • @endscene665 hardened outbound integration webhooks against SSRF.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.10.5...v0.11.0

May 19, 2026
v0.10.5

v0.10.5

Fixes

  • Emoji rendering in comments. Emojis inserted via the picker now render correctly in saved comments instead of disappearing.
  • Enter selects from the emoji picker. Pressing Enter while the emoji picker is open picks the highlighted item instead of inserting a newline.

Improvements

  • Workspace-unavailable UX. Suspended or otherwise unavailable workspaces now show a consistent, friendly message at sign-in and on the workspace page itself.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.10.4...v0.10.5

May 19, 2026
v0.10.4

v0.10.4

Features

  • Faster managed-cloud onboarding. New workspace.onboardingComplete flag in the config-file schema lets the control plane mark the workspace as set-up at provision time, so CP-provisioned tenants skip the OSS /onboarding wizard and land straight at /admin.
  • Magic-link auto-redirect. /verify-magic-link now auto-triggers the verify endpoint on mount with a short delay (preserves the email-prefetch defense), and hides the manual Continue button for the first 5 seconds so the happy path lands without a competing CTA.

Fixes

  • SSR window crash on magic-link verify. The verify URL is now constructed inside useEffect, so SSR doesn't crash on a missing window.
  • Comment content in portal view. contentJson is now passed through when mapping comments for portal rendering, so rich-text comments render correctly on the public side.

Reliability

  • Stale-summary sweep hardening. Added a circuit breaker and per-board deduplication so a single failing summary refresh can't cascade across the queue.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.10.3...v0.10.4

May 18, 2026
v0.10.3

v0.10.3

Improvements

  • Magic-link OAuth in the config-file auth schema. The oauth.magicLink block is now accepted in config-file driven setups.

Fixes

  • Mentions avatars. Mention chips fall back to user.image when the principal avatar columns are empty, so suggestions render correctly for users without a dedicated avatar record.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.10.2...v0.10.3

May 16, 2026
v0.10.2

v0.10.2

Improvements

  • Post @-mentions. Type @ in a post to mention a team member or portal user. Mentioned users get an in-app notification and an email, with the email respecting unsubscribe-all preferences. Mention chips render with the author's current display name and expand to a hover-card preview.
  • Rich text editor for comments. Comments now support headings, bold, italic, code blocks, lists, links, and an emoji picker. Existing markdown comments keep rendering as before.
  • Welcome card on the portal home. New admin setting that puts a customisable greeting at the top of the public feedback list. Drafts stay editable while the card is disabled so you can prep an announcement before flipping it on.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.10.1...v0.10.2

May 14, 2026
v0.10.1

v0.10.1

Improvements

  • New-device sign-in email is always on. The per-workspace toggle has been removed. New-device notification emails are a sensible security default and no longer need configuration.
  • Cleaner team authentication settings. "Require 2FA" moved into its own "Team security policy" card, separate from the sign-in methods list, with copy and spacing aligned to the Portal tab.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.10.0...v0.10.1

May 14, 2026
v0.10.0

v0.10.0

Features

  • Single sign-on with custom OIDC. Connect any OpenID Connect provider as its own sign-in card, separate from the social login grid. A built-in Test sign-in flow runs a live diagnostic handshake so you can verify the connection before rolling it out.
  • Two-factor authentication. Users can enrol in TOTP-based 2FA from their profile; admins can require 2FA workspace-wide for password sign-in or reset another user's enrollment.
  • Recovery codes. Generate one-time break-glass codes to sign in when SSO or 2FA is unavailable.
  • SSO enforcement. Require SSO for verified email domains, so members on those domains can only sign in through your identity provider.
  • Security audit log. A new feed records security-sensitive actions (auth config changes, SSO secret updates, 2FA resets, domain enforcement, sign-ins) with an admin UI to review them.
  • Sign-in defenses. Sign-in attempts are now rate limited, and signing in from a new device sends a notification email.
  • SSO provisioning controls. Choose which role JIT-provisioned SSO users receive, and map roles from IdP claims via configurable attribute mapping.
  • Declarative configuration file. Quackback can read settings from `/etc/quackback/config.yaml` and keep them reconciled; managed fields are locked in the admin UI so the file stays the source of truth.
  • Workspace lifecycle states. Workspaces now have an explicit state (active / suspended / deleting) with an inline overlay and appropriate responses when not active.
  • Reorganized admin settings. API Keys, Webhooks, and MCP are now one tabbed API page; Members, Integrations, and Security are grouped under Administration; SSO has its own page with a status chip in the nav.

Bug fixes

  • Pinned comment restored on public posts. A pinned comment no longer disappears from the public post detail view.
  • Default post statuses on first migrate. Fresh installs now seed the default post statuses.
  • 2FA redirect preserves callback URL. The intended destination is kept through the 2FA challenge redirect.

Performance

  • Queue hardening. OSS BullMQ queues share a single Redis connection, drain gracefully on shutdown, use bounded retention, and dedupe jobs by ID for idempotency.

Internal

  • Per-feature tier-limit gates with internal endpoints and structured exception dispatch.
  • UserVoice import CLI supports incremental top-up; the REST import API accepts an author attribution override.
  • Combined magic-link + OTP sign-in email.

Tests

  • Extensive new coverage across SSO, 2FA, audit logging, recovery codes, and sessions.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.9.9...v0.10.0

May 1, 2026
v0.9.9

v0.9.9

Features

  • Per-board Discord channels. Discord notifications now support per-channel routing with board filters, matching Slack. Add multiple channels, scope each to a specific board, and pick which events fire (post created, status changed, comment created).

Bug fixes

  • Add Channel dialog state reset. The Add Channel dialog now clears form state when closed via Cancel or X, so reopening starts fresh instead of carrying over leftover input.

Internal

  • Shared routing-table UI between Slack and Discord extracted into a single NotificationChannelRouter component. One-time migration cleans up legacy duplicate event-mapping rows for chat integrations.

Tests

  • New Playwright e2e coverage for the Discord routing flow and Slack routing parity.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.9.8...v0.9.9

April 29, 2026
v0.9.8

v0.9.8

Features

  • Filter chips on the public feedback portal. A new chip-based filter UI replaces the legacy Filter button. Status, Tag, Vote count, Created date, and Team-response filters can each be added, swapped, or removed inline; chips are translated across all 6 locales. Boards joined the chip system on this release, so the mobile board sheet has been retired in favour of the unified filter UI.
  • Roadmap toolbar parity. The public roadmap page now shares the feedback page's toolbar pattern: searchable Sort combobox, Search popover, and a Filter button on a single row across desktop and mobile. The roadmap selector is a horizontal scrolling tab strip with snap-to-column behavior, and Kanban columns scroll horizontally with chevron + fade affordances and an internal column scroll capped to viewport height.
  • More filter dimensions on the public portal. Public post queries now respect minVotes, dateFrom, and responded filters. Complete and closed posts are hidden by default unless a Status chip overrides it.

Performance

  • Faster cold start. Nitro now lazy-loads SSR chunks and the bootstrap path uses an auth fast-path. Bundles dedup shared deps, the Docker image switched to an Alpine base, the database is pre-warmed at boot, and migrations are bundled into the runtime.

Bug fixes

  • Calendar-invalid date filters are rejected. `dateFrom` strings that look syntactically valid but aren't real dates (e.g. Feb 30) now fail validation instead of returning empty results.
  • EXISTS subquery on public post listings. Matches the admin path's `${posts.id}` interpolation so the duplicate-suggestion-aware filter works on the portal too.

Internal

  • Promoted `toggleItem`, `CircleIcon`, `MenuButton`, `VOTE_THRESHOLDS`, `DATE_PRESETS`, and `RespondedFilter` to `components/shared` / shared types so admin and portal filter UIs reuse the same primitives.
  • /simplify pass: memoization, hoisted icon maps, and pruned dead code across the new portal toolbar/filters surfaces.
  • Filter message IDs migrated to chip-based keys; widget board placeholder + portal "Upvotes" label wrapped in `FormattedMessage`.

Tests

  • New Playwright e2e coverage for the chip filter flow and active-by-default hint.
  • Unit tests for the Board filter category, single-board collapse, and the new public post filter dimensions.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.9.7...v0.9.8

April 27, 2026
v0.9.7

v0.9.7

Performance

This release reduces server-side render times under concurrent load and shrinks the JavaScript footprint of every page. Both improvements are most visible on busy boards and admin pages with many simultaneous viewers.

  • Hot data on the server-render path (workspace settings, OAuth provider config, user role lookups) is now cached more aggressively so most page renders only do a single fast lookup instead of multiple database queries.
  • Per-route bundles were merged into per-section groups so the browser fetches a handful of larger chunks instead of dozens of tiny ones.
  • Sensitive credentials remain off the cache layer — only metadata about which integrations are configured is cached, not the secrets themselves.
  • Removed a duplicate database query that was firing on every authenticated page load.

Features

  • Edit your own comments. Comment authors and team members can now inline-edit comments after posting. Edited comments show an (edited) marker. (#149)
  • Set help-center article author via API and MCP. Articles created or updated through the API/MCP can now specify an author principal. Internal: this came alongside an API-layer cleanup that standardises how endpoints handle authentication and ID validation. (#147)

Bug fixes

  • S3 uploads on self-hosted Docker Compose. When S3_PROXY=true, presigned uploads are now proxied through the server instead of returning a URL the browser cannot reach. Fixes deployments where MinIO is only reachable on the internal Docker network. (#150)
  • Widget changelog scroll. Restored vertical scroll on the changelog detail view inside the embeddable widget.
  • Cmd+Enter in the post editor. Cmd+Enter inside the comment textarea now submits the comment instead of also saving the post; Cmd+Enter on the post itself only saves when there are pending changes. (#144)

Internal

  • Enforced the client/server import boundary so server-only modules (node:crypto, ioredis, bullmq) can no longer be pulled into the browser bundle through accidental imports.
  • Expanded Playwright e2e coverage with 25 new spec files (~400 tests) over previously untested areas. (#148)
  • Added unit tests covering the new caching surfaces.

Full changelog: https://github.com/QuackbackIO/quackback/compare/v0.9.6...v0.9.7

April 20, 2026
v0.9.6

v0.9.6

Bug fixes

  • Restored the max-width container on post detail pages, which was accidentally removed during the help center routing restructure in v0.9.5 (#146)

Tests

  • Added a Playwright regression test that asserts post detail content is constrained within its max-width container
April 18, 2026
v0.9.5

v0.9.5

What's changed

  • Help center categories use icons - The emoji picker for help center categories has been replaced with a Heroicons picker for consistent iconography.
  • Fix article editor layout - The article body now scrolls independently while the header stays fixed.
  • Fix widget default board - The new post form in the widget now opens with the configured default board selected.
  • Smoother widget launcher animation - Launcher fade-in and content load feel more polished.
  • Clear default board in widget settings - The default board field now has a clear button to unset the value.
  • Fix settings not refreshing - Settings changes now take effect immediately after saving.
April 17, 2026
v0.9.4

v0.9.4

What's changed

  • Help center shows categories with nested articles - Parent categories whose articles lived under sub-categories were hidden from the public help center. They now appear with a total count that includes the whole subtree.
  • Admin help center shows subtree article counts - Parent categories display "direct / total" so editors can see where articles actually live.
  • @quackback/widget on npm - npm install @quackback/widget to embed Quackback in your app. TypeScript types and a React adapter (useQuackbackInit, useQuackback, useQuackbackEvent) included.
  • Widget security hardening - Stricter instanceUrl validation and hardened window.open calls.
  • Fix widget theme colors - Configured colors now apply consistently.
  • Fix dark mode flash on navigation - Dark mode no longer flickers during client-side route changes.
April 16, 2026
v0.9.3

v0.9.3

What's changed

  • Fix URLs breaking post submit - TipTap link marks with null attrs (e.g. title: null) were rejected by Zod validation, preventing posts with auto-linked URLs from being submitted
  • Fix raw HTML/markdown in post previews - Post card descriptions now strip HTML tags and markdown formatting instead of showing raw syntax like <p>text</p> or [link](url)
  • Consolidate content preview utility - Removed duplicate truncateContent functions across widget and help center, replacing them with a shared contentPreview() that handles both stripping and truncation
  • Standardize widget typography - Consistent text sizing across all widget views: bumped help center category titles/descriptions, unified metadata labels, form buttons, badges, and action links
  • Fix help article scroll overflow - Article content in the widget now scrolls properly when it overflows the container
  • Fix help article portal link - "View on portal" from widget help articles now opens the correct Quackback URL instead of the host site
April 15, 2026
v0.9.2

v0.9.2

What's new

  • Help center category hierarchy -- Organize articles into nested categories up to 3 levels deep with cascade soft-delete, 30-day restore window, and parent-chain validation (#132)
  • Help center inline in portal -- /hc/* now renders under the portal shell with a Help Center tab in the portal nav; standalone subdomain and custom-domain support removed in favor of a single unified portal
  • Full-page article editor -- Replaces the old dialog-based editor with an Intercom-style page at /admin/help-center/articles/$articleId: slim top bar with category pill and publish state, reader-width body, description subtitle, rich editor with images and embeds
  • Publish → View article flow -- Once an article is published, the Publish button swaps to a green "View article ↗" link that opens the portal URL in a new tab; Unpublish moves to an overflow menu
  • Admin finder redesign -- Sidebar category tree that auto-expands the ancestor chain of the selected category, hover-reveal row actions for + sub / edit / delete, breadcrumb row, sub-category chip row for lateral navigation, skeleton loader, deleted items view
  • Auto-rehost external images on article save -- LLM-authored image embeds now get fetched (SSRF-guarded, magic-byte verified) and rehosted to workspace S3 automatically
  • Settings nav regrouped -- General / Customization / Feedback / Help Center / End Users / Developers, dropping the "Portal" umbrella and pulling Widget alongside Branding under Customization
  • Portal + Permissions pages merged -- /admin/settings/portal was split across two pages by auth state (signed-in vs anonymous); now consolidated into /admin/settings/permissions grouped by action, with signed-in and anonymous toggles per action
  • Button pills everywhere -- New `shape` variant on the Button component defaulting to pill (opt out with `shape="default"`), making admin buttons consistently rounded without per-call class overrides

Bug fixes

  • Fix help center article canonical URL missing `/hc` prefix -- og:url and rel=canonical now correctly point at `{baseUrl}/hc/{category}/{article}` (#132)
  • Fix restoreCategory allowing a child to be restored under a still-deleted parent, which would leave the category orphaned from the active tree -- now throws PARENT_DELETED and admins must restore the ancestor chain top-down (#132)
  • Fix help center finder infinite scroll sentinel never observed on first category selection -- the IntersectionObserver was attached to a null ref when the sentinel was only conditionally mounted (#132)
  • Fix stale closure in HelpCenterCategoryTree toggle() that could read outdated ancestorIds under concurrent mode (#132)
  • Fix help center admin nav links font weight + header hierarchy for better readability

Housekeeping

  • Rename TypeID prefixes: `helpcenter_article` → `article`, `helpcenter_category` → `category`, `helpcenter_feedback` → `article_feedback`. No data migration required -- TypeIDs are stored as raw uuid columns and prefixes only apply at serialization time
  • Drop dead `kb_domain_verifications` table and `helpcenter_domain` type after custom help center domain support was removed earlier in the branch
  • Delete dead `packages/db/src/utils.ts` generateId helper, shadowed by `@quackback/ids` generateId(prefix)
  • Branding preview page rewritten to mirror the real feedback portal layout (collapsed "What's your idea?" header, boards sidebar, per-post cards, Powered by Quackback pill with duck logo)
  • Extract CategoryActions shape to collapse sprawling category callback props through HelpCenterList → FiltersPanel → Tree
April 10, 2026
v0.9.1

v0.9.1

What's new

  • Tag editor -- Manage tags from Admin > Settings > Tags with name, description, and color. Tags render as colored badges throughout the app. (#130)
  • Status editor improvements -- Auto-save on every change (no more save/discard bar), hex color input with randomize button, edit dialog for existing statuses, roadmap accepts any number of statuses
  • Per-field save spinners -- Inline ArrowPathIcon spinner on the specific toggle being saved across widget, status, tag, and permissions settings

Bug fixes

  • Fix status/roadmap reorder failing with cannot cast type record to uuid[] -- use Drizzle query builder with inArray instead of raw SQL ANY()
  • Fix tag description clearing silently ignored (null converted to undefined)
  • Fix tag list not updating immediately after create/edit
  • Fix popover scroll inside dialogs -- popovers now auto-portal to dialog content instead of document.body, so react-remove-scroll doesn't block wheel events
  • Fix native scrollbar showing in tag add popover -- use Radix ScrollArea with styled scrollbar

Housekeeping

  • Unify help center embeddings to text-embedding-3-small (same model as feedback pipeline)
  • Large codebase cleanup: deduplicate OAuth/webhook components, consolidate AI utilities, extract shared Redis config, remove dead code
  • Migrate widget identify from HMAC to JWT-only with server-side token signing
  • Support custom user attributes in widget JWT claims
  • Remove unused feedbackSignalCorrections table
April 8, 2026
v0.9.0

v0.9.0

What's new

  • Standalone help center (experimental) -- Build and publish a help center directly from Quackback. Create categories and articles with the rich text editor, then serve them on a standalone subdomain with search, SEO, and structured data. Enable via Settings > Advanced > Experimental. (#128)
  • Help tab in widget -- Browse help center categories and search articles without leaving the feedback widget. Drill into categories to see article lists, or search across everything. (#128)
  • Help center MCP tools -- Manage categories and articles programmatically via MCP, with a new quackback://help-center/categories resource for discovery. (#128)
  • Help center API -- Full REST API at /api/v1/help-center for categories and articles with CRUD, publish/unpublish, and article feedback endpoints. (#128)
  • Russian translations -- Full Russian locale for the portal and widget by @TAZAQ. (#126)
  • API-only imports -- Import system simplified to use the REST API exclusively, removing direct DB mode. (#127)

Fixes

  • Bubble menu clipping -- Fixed the editor bubble menu getting clipped inside dialog modals.
April 2, 2026
v0.8.1

v0.8.1

Fixes

  • Portal navigation — Removed the Help Center tab from the public portal. Help center will become its own dedicated portal in a future release. The tab was previously visible even when the feature flag was turned off.
April 2, 2026
v0.8.0

v0.8.0

What's new

  • Mobile native SDK support -- New sendToHost bridge abstraction replaces direct postMessage calls, enabling native mobile SDK integration for iOS and Android. The bridge falls back to postMessage in web contexts for full backwards compatibility.
    • quackback-ios -- Swift SDK for iOS
    • quackback-android -- Kotlin SDK for Android
  • Full-screen mobile widget -- Widget renders full-screen on mobile with a close button and CSS-based responsive layout. Smooth slide-up/slide-down transitions replace the desktop popover on viewports under 640px.
  • Internationalization -- Portal and widget now support English, French, German, Spanish, and Arabic with full RTL support. Auto-detects browser language via Accept-Language, with explicit locale override via SDK config or ?locale= param.
  • Auto-upvote on post creation -- Authors automatically upvote their own posts, with the vote recorded atomically in the same transaction.
  • Mobile SDK locale support -- iOS and Android SDKs now pass locale via both URL param and postMessage for flicker-free i18n.
  • Rich editing for portal users -- Users editing their own posts now have full editor features: headings, code blocks, task lists, dividers, slash commands, and images.
  • Slash command hints -- Editor placeholders now show "Type / for commands" across all locales to improve discoverability.

Fixes

  • Widget placement CSS on re-init -- Style tag is now properly cleaned up on destroy, preventing stale left/right positioning when reinitializing with a different placement.
  • Image paste in admin -- Fixed Zod validation crash when pasting images with undefined attrs (e.g. caption: undefined from ResizableImage extension).
  • Slash commands in admin -- Global / search hotkey was intercepting keystrokes in TipTap editors. Now skips contentEditable elements.
  • Post modal feature parity -- Edit post modal now has full editor features (images, slash menu, code blocks, tables) matching the create dialog. Saves also close the modal.
  • Team members query crash -- Switched from useSuspenseQuery to useQuery with fallback to prevent crashes during navigation.