Tightknit Release Notes (Dec 10, 2025): Filter by Bots
Tightknit Release Notes (Dec 10, 2025)
Tightknit Release Notes (Dec 10, 2025)
🤖👶 Filter by Humans or Bots in the Studio
We're introducing a new filter in the Studio to organize your user-related analytics based on bot status. If, for example, bot auto-replies consist of a significant amount of messages in your community, you may want to filter by "only Humans" in your results. Or perhaps you have very targeted app responses and want to measure their impact ‒ you may then want to filter only by bots. This filter is available on the Overview page and all the primary list view pages in the Studio.
Companion Site
Users are now returned to the original page on the site they were attempting to access prior to logging in
Added back button to Event detail page
Fixed format for dates in the JSON-LD metadata of Post and Event pages to improve SEO results
Fixed bug where custom fonts were not applied to post and comment bodies
Companion sites on the default .tightknit.community Tightknit domain now perform a canonical redirect to the site's custom domain, if one is configured
Renamed the Events list view page query param from events_list.view to view
Fixed bug that would fail subsequent SSO logins to authenticated sites
Added setting to auto-reveal feed post file attachments, that is default off
Fixed zoom cropping default logo on hover of feed blog post cards
Increased max height above "see more" threshold of feed post snippets
Upgraded react and Next-related dependencies to protect against CVE-2025-55182 vulnerability
Slack
When file attachments on messages of an admin user fail to sync to Tightknit, the warning is now DMed to the admin in addition to the ephemeral threaded reply
Updated invalid URL slug error message when configuring custom navigation menu items settings to include the slug validity rules
Studio
Added "Type" filter to filter results by human vs. bot Slack users
Added "Joined Date" filter on the Members page
Improved performance on the Activities page
API
⚠️ Scheduled breaking change (12/16/2025): The error property on Admin API failure responses will change from an error message string to a JSON object containing properties: code and message. Please update your code's error handling to prepare for this change.
