Outlit Changelog - Mid-February 2026

Slack Bot – @mention Outlit in any Slack channel to ask questions about your customers. The bot streams responses directly in-thread, with full access to your customer data, timelines, and revenue metrics via the same tools powering the MCP server.
Fact Extraction – Outlit now passively listens to your Slack conversations and uses AI to automatically extract customer facts — feature requests, pain points, product feedback, sentiment signals, and more. Facts are categorized, linked to the right customer profiles and contacts, and stored as structured evidence so nothing slips through the cracks.
Clerk Authentication Integration – Connect Clerk to import your existing users and organizations as customers, just like Stripe and Supabase. Available from the customers page.
Agent-Assisted SDK Setup – Setting up the Outlit SDK is now guided entirely by an installable agent skill. The onboarding flow and tracking settings page point users to install the skill, which handles framework-specific setup through your AI assistant. Manual installation tabs have been removed in favor of this streamlined experience.
MCP Skill Recommendations – The MCP integration settings page now recommends installing Outlit agent skills for better query guidance and best practices when using AI assistants.

Consent Management & disableTracking() – New privacy-first API for managing user consent. Call disableTracking() to immediately stop all tracking, flush pending events, and persist the consent state across sessions. Available in React hooks, Vue composables, the singleton API, and the CDN script.
Client Prop for OutlitProvider – Pass a pre-configured Outlit client instance directly to the React OutlitProvider via a new client prop, matching PostHog's provider pattern. When provided, the provider skips creating a new instance and the caller owns the lifecycle.
Auto-Identify from Unnamed Email Inputs – The browser SDK now detects email addresses from form inputs that don't have a name attribute. React/JSX controlled components often omit name attributes, causing auto-identify to miss them — this is now handled.
Configuration options trackCalendarEmbeds, trackEngagement, and idleTimeout are now correctly forwarded to the tracker when set via the provider.

Fixed identifier source for browser-identified customers, ensuring the correct identity is attributed.
Fixed SQL query builder validation to prevent invalid window size parameters.
Fixed duplicate Slack app_mention events from being processed multiple times via a deduplication guard.
Fixed session ID preservation when flushing events during a disableTracking() call.
MCP API endpoints now use a restricted, org-scoped database client with row-level security policies enforced per query.