Statsig Release Notes
276 release notes curated from 285 sources by the Releasebot Team. Last updated: Nov 18, 2026
- Nov 17, 2026
- Date parsed from source:Nov 17, 2026
- First seen by Releasebot:Nov 18, 2026
- Modified by Releasebot:Nov 18, 2026
🔬 Agent Experimentation
Statsig releases Agent Experimentation, now available to everyone, helping teams version AI configs, compare agent versions with offline and online evaluations, and run experiments to measure real-world impact on customer outcomes.
🔬 Agent Experimentation
Move past a simple eval score to get a rigorous, holistic picture of how agentic features perform and improve.
What you can do now
- Version prompts, models, and settings with AI configs.
- Compare agent versions with offline evals.
- Learn from real customer interactions with online evals.
- Run experiments to measure impact on task completion, conversion, retention, and more.
Why this matters
When eval scores go up, does that actually make your product better? The only way to know whether a change to an AI feature truly works is to validate it with real users and real outcomes. Agent Experimentation lets you connect what scores well with what works for your customers, and use what you learn to improve the next version of your agentic feature.
Try it out
Agent Experimentation is now available to everyone in Statsig. Learn more in the Agent Experimentation docs or the launch blog.
Original source - Oct 9, 2026
- Date parsed from source:Oct 9, 2026
- First seen by Releasebot:Oct 13, 2026
🎛️ Filter Dashboards by Experiment Status
Statsig adds Experiment Status filters to dashboards, helping teams focus on running experiments while keeping layouts intact. Users can share filtered views by URL, save a default filter, and see nonmatching widgets dimmed.
🎛️ Filter Dashboards by Experiment Status
Dashboards can now focus on the experiments that are running right now.
What you can do now
- Choose Add Filter → Experiment Status on any dashboard, including dashboards generated automatically from tags
- Share the filtered view by URL, or save your selection as the dashboard’s default filter
- Experiment widgets that don’t match the filter are dimmed in place, so your layout stays intact
Why this matters
Experiment overview dashboards get cluttered as tests start and finish. Now you can keep the view focused on running experiments without removing widgets by hand.
Try it out
Open any dashboard, choose Add Filter, and select Experiment Status.
Original source All of your release notes in one feed
Join Releasebot and get updates from Statsig and hundreds of other software products.
- Oct 8, 2026
- Date parsed from source:Oct 8, 2026
- First seen by Releasebot:Oct 13, 2026
👀 Preview Changes
Statsig now lets users preview proposed gate and dynamic config changes in review modals, compare visual and diff views, filter rules, find reviewers, and turn on Slack notifications—helping catch issues before approval.
👀 Preview Changes Before Requesting a Review
You can now verify a proposed gate or dynamic config change inside the review modal before you submit it for approval.
What you can do now
- Toggle a preview with Visual and Diff views, and filter between Changes and All Rules
- See compact comparisons that highlight the changed fields when requesting a review for rule changes
- Find reviewers faster with a searchable selector for Teams and Individuals, with checkboxes and removable pills
- Get a prompt in the review flow to turn on Slack notifications for reviews
Why this matters
Reviewers can only approve what they can clearly see. Now you can check exactly what you are proposing before you send it, which means fewer review rounds spent on mistakes you could have caught yourself.
Try it out
Request a review on a gate or dynamic config rule change and open the preview in the review modal.
Original source - Oct 8, 2026
- Date parsed from source:Oct 8, 2026
- First seen by Releasebot:Oct 13, 2026
🩺 Warehouse Export Observability
Statsig adds warehouse export observability with failure email notifications, error details in the UI, a status API endpoint, and MCP assistance to help teams spot and diagnose failed exports.
🩺 Warehouse Export Observability
You can now see when a warehouse export fails and why, without guessing or contacting support.
What you can do now
- Get a failure notification email when an export fails
- See the error message in the UI so you understand why an export failed
- Query export success and failure status programmatically with the new list-warehouse-export-status endpoint
- Ask the Statsig MCP to help you understand an export failure
Why this matters
A failed export used to be easy to miss and hard to diagnose. Now you hear about failures right away and can see the cause, in the UI, over the API, or through your AI tooling.
Try it out
Learn more in the Warehouse Exports docs and the export status API reference.
Original source - Oct 6, 2026
- Date parsed from source:Oct 6, 2026
- First seen by Releasebot:Oct 13, 2026
🔐 Entity-Level Create Permissions
Statsig adds role-based permissions for creating entities, giving teams finer control over who can create each entity type.
🔐 Entity-Level Create Permissions
Role permissions now extend to creating entities, not just editing and deleting them.
What you can do now
- Control who can create each entity type through role permissions, alongside the entity-level edit and delete permissions already available
Why this matters
You can now decide who is allowed to create new entities, so roles can match how your teams actually work without being over-permissioned.
Try it out
Learn more in the Statsig Access Management docs.
Original source Similar to Statsig with recent updates:
- Google release notes2534 release notes · Latest Nov 18, 2026
- Notion release notes242 release notes · Latest Nov 16, 2026
- Grammarly release notes12 release notes · Latest Aug 13, 2026
- Anthropic release notes964 release notes · Latest Nov 18, 2026
- OpenAI release notes1264 release notes · Latest Nov 18, 2026
- Figma release notes186 release notes · Latest Nov 17, 2026
- Oct 1, 2026
- Date parsed from source:Oct 1, 2026
- First seen by Releasebot:Oct 13, 2026
🤖 Statsig MCP v3
Statsig releases MCP V3 with a leaner set of default tools, on-demand access to more Console API operations, and self-serve controls for managing user and project access.
The Statsig MCP is now leaner for agents and covers far more of the Console API.
What you can do now
- Work with 18 default tools instead of 93, so agents spend less context on tool definitions and choose the right tool more easily. Additional operations are discovered on demand
- Use api_read, api_write, and api_destructive to discover and run Console API operations across Statsig without needing a dedicated MCP tool for each one
- Manage which users and projects can use MCP with self-serve access controls
Why this matters
Agents work better when they carry fewer tool definitions and can reach more of the platform. V3 gives you both, with governance you control.
Try it out
Learn more in the Statsig MCP Overview.
Original source - Sep 16, 2026
- Date parsed from source:Sep 16, 2026
- First seen by Releasebot:Oct 13, 2026
🎯 Choose Features for Contextual Bandits
Statsig now lets teams choose which context features cloud contextual bandits use for training, giving them more control over what models learn.
🎯 Choose Features for Contextual Bandits
You can now specify which context features a cloud contextual bandit trains on.
What you can do now
- Select the features in your context that the ML model should use for training
Why this matters
Not every attribute in your context should drive the model. Choosing the features yourself gives you control over what the bandit learns from.
Original source - Sep 15, 2026
- Date parsed from source:Sep 15, 2026
- First seen by Releasebot:Oct 17, 2026
🧹 Stale Dynamic Config Management
Statsig adds advisory stale-config management, helping teams identify Dynamic Configs for cleanup, understand why they were flagged, and manage lifecycle states with configurable inactivity windows, reminders, and Console API filters—without changing runtime behavior.
🧹 Stale Dynamic Config Management
Dynamic configs can live for years without a clear cleanup point. Teams can now find likely cleanup candidates, understand why they were flagged, and decide what to do next.
What you can do now
- Temporary, Permanent, and Stale lifecycle states, with filtering in the Dynamic Config catalog
- Reason-specific guidance on the config page: configs with no recent checks can be archived, while intentionally long-lived configs can be marked Permanent
- A team-defined inactivity window (15, 30, 60, or 90 days; 30 by default)
- Periodic email, in-app, and Slack reminders based on notification preferences
- Lifecycle fields and filters in the Console API
Note: This is advisory only. A stale label does not change evaluation, disable a config, or archive anything automatically. This rollout does not include Feature Gate-only automation such as auto-archive, code-cleanup prompts or PRs, or bulk cleanup.
Why this matters
This closes a governance gap that several customers have raised and makes cleanup easier without introducing runtime risk.
Try it out
Check out the Feature Management page in your Statsig Console to evaluate config staleness.
Original source - Sep 12, 2026
- Date parsed from source:Sep 12, 2026
- First seen by Releasebot:Sep 17, 2026
🔐 Self-Serve RBAC for MCP
Statsig adds self-serve RBAC for MCP, letting teams manage project-level and role-level access in the console with read only or read and write controls for safer AI-assisted exploration.
🔐 Self-Serve RBAC for the Statsig MCP
You can now manage MCP access directly in the console, with project-level and role-level controls.
What you can do now
- Set a project-level MCP scope — No access, Read only, or Read and write — as the ceiling for all roles in that project.
- Configure MCP access per role within that project maximum, including Member and custom roles.
- MCP only exposes tools that the project scope, role permissions, and token scope all allow.
To configure:
Go to Project Settings > Roles to set Default Project MCP Scope, then open a role's Permissions > MCP to configure its access.
Why this matters
Before this, teams that wanted to give analysts or stakeholders AI-assisted exploration through the MCP had no way to cap what they could do. Now, you can give some users read-only MCP access for exploration while keeping write access to the people who need it.
Try it out
Go to Project Settings > Roles in the Statsig console to configure MCP access for your team.
Learn more in the Statsig MCP Overview.
Original source - Sep 1, 2026
- Date parsed from source:Sep 1, 2026
- First seen by Releasebot:Sep 3, 2026
🔐 Entity-Level Edit and Delete Permissions
Statsig introduces granular role permissions that separate edit and delete access by config type, including Gates, Experiments, Segments, Layers, Autotunes, Parameter Stores, Prompts, and more. Enterprise teams can now match access to real ownership without over-permissioning.
Role permissions now let you control edit and delete access separately for each config type.
What you can do now
Each role can now be configured with independent edit and delete permissions for:
Gates · Holdouts · Dynamic Configs · Segments Experiments · Layers · Autotunes · Parameter Stores · Prompts
Why this matters
Before this, permissioning wasn't specific and allowed for broad experiment and gates access. Now, you can define roles that match how your teams actually own and operate different config types, without over-permissioning anyone.
Try it out
Available now for all Enterprise customers. Go to Settings in the Statsig console to configure granular permissions per role.
Learn more in the
Statsig Access Management docs
Original source
. - Aug 21, 2026
- Date parsed from source:Aug 21, 2026
- First seen by Releasebot:Sep 3, 2026
🧪 Richer Experiment Configuration via MCP
Statsig adds five new experiment fields in the MCP, giving teams fuller control over setup with secondary ID types, identifier mapping, non-prod environments, secondary metrics, and external links without using the console.
Create_Experiment and Update_Experiment_Entirely now accept five additional fields, giving you fuller control over experiment setup through the MCP.
What you can do now
Five new fields are now accepted by Create_Experiment and Update_Experiment_Entirely :
secondaryIDType identifierMappingMode enabledNonProdEnvironments links secondaryMetrics
Why this matters
Now, you can set secondary ID types, identifier mapping, non-prod environments, secondary metrics, and external links without falling back to the console.
Try it out
If you have the Statsig MCP set up, try a prompt like:
"Using the Statsig MCP, create an experiment with a secondary metric of revenue and enable it in staging."Learn more in the Statsig MCP Overview.
Original source - Aug 21, 2026
- Date parsed from source:Aug 21, 2026
- First seen by Releasebot:Sep 3, 2026
🔐 SCIM Role Aliases for Custom IdP Naming Conventions
Statsig adds SCIM role aliases, letting teams map existing identity provider role names to Statsig roles without renaming groups. The self-serve setup works with Okta, Microsoft Entra ID, and other SCIM-compatible providers for easier provisioning.
You can now map your identity provider's role names to Statsig roles without renaming anything in your IdP.
What you can do now
- Create aliases on the Statsig side that translate your IdP's existing role names to first-class Statsig roles. Works with Okta, Microsoft Entra ID, and other SCIM-compatible identity providers with strict or unchangeable naming conventions.
- Self-serve setup in a few clicks. No support ticket or manual intervention needed
Why this matters
Now, SCIM provisioning no longer requires your IdP group names to match an expected role format. You can define the translation on the Statsig side and let provisioning work with whatever names your IdP already uses.
Try it out
Go to Settings in the Statsig console to configure SCIM role aliases for your organization.
Original source
Learn more in the Statsig SCIM docs. - Aug 21, 2026
- Date parsed from source:Aug 21, 2026
- First seen by Releasebot:Sep 3, 2026
🔭 Pipeline Overview Auto-Provisions for Athena Connections
Statsig now automatically provisions the Pipeline Overview dashboard for new Athena Warehouse Native connections, giving teams pipeline visibility from day one without manual repair or setup.
New Athena Warehouse Native projects now get the Pipeline Overview dashboard set up automatically on connection creation.
What you can do now
- Get the Pipeline Overview dashboard, metric source, and pipeline table created automatically when setting up a new Athena connection
- No manual repair or setup step needed to get DAG and pipeline visibility from day one
Why this matters
Before this, new Athena projects skipped the Pipeline Overview provisioning step entirely, leaving teams with no pipeline observability until someone ran a manual repair. Now, you get full pipeline visibility out of the box from the moment your connection is created.
Try it out
Create a new Athena Warehouse Native connection in the Statsig console to see the Pipeline Overview dashboard provisioned automatically.
Original source
Learn more in the Statsig Warehouse Native docs. - Aug 20, 2026
- Date parsed from source:Aug 20, 2026
- First seen by Releasebot:Sep 3, 2026
🩺 Experiment Daily Checks Now Available via Console API
Statsig adds an API for experiment Daily Checks data, letting teams pull diagnostics directly, use flexible date ranges, and automate checks or alerts from the same signal shown in the console.
You can now pull the data behind the Daily Checks column in the experiment list directly over the API.
What you can do now
One new endpoint is available on statsigapi.net/console/v1/ :
GET /console/v1/experiments/{id}/diagnostics_checks?lastDays=30- Use lastDays (1-90) to set a lookback window without computing dates yourself
- Use startDate / endDate if you need an explicit range instead
- is_realtime tells you whether the final day is still filling, so you know not to treat it as a complete day
- Warehouse Native experiments now return real data from the warehouse exposures summary, the same source the console list column uses
Why this matters
Before, the Daily Checks column in the experiment list flagged experiments that were "In Progress" after being pulled from code, or "Decision Made" while still serving traffic and catching those states meant querying your own warehouse. Now, you can surface that signal programmatically and build automated checks or alerts on top of it.
Try it out
Review the full API reference in the Statsig Console API docs.
Original source - Aug 19, 2026
- Date parsed from source:Aug 19, 2026
- First seen by Releasebot:Sep 3, 2026
💰 Query Cost Attribution
Statsig adds warehouse native query cost attribution tags for WHN, letting teams trace compute spend back to specific experiments, gates, job types, and reload IDs across Snowflake, BigQuery, Redshift, and Databricks.
💰 Warehouse Native Query Cost Attribution
Statsig WHN queries now carry cost attribution tags in your warehouse, so you can see exactly what Statsig activity is driving your compute costs.
What you can do now
Every query is stamped with is_whn, a type (experiment, gate, etc.), the experiment or gate name, a job type, and the reload ID. Tags land natively in each warehouse — nothing leaves your account:
- Snowflake — session QUERY_TAG in ACCOUNT_USAGE.QUERY_HISTORY and QUERY_ATTRIBUTION_HISTORY
- BigQuery — job labels (type=whn_query) in INFORMATION_SCHEMA.JOBS
- Redshift — query_group in SYS_QUERY_HISTORY.query_label
- Databricks — statement comment in system.query.history
Why this matters
Before , you could see total spend but had no way to attribute it to a specific experiment or job type in Statsig. Now, you can point one query at your warehouse's usage view, filter to Statsig WHN queries, group by experiment, and get per-experiment reload cost, making it straightforward to spot expensive reloads and change your schedule.
Try it out
Filter your warehouse usage view to is_whn:"True" (or type=whn_query on BigQuery) and group by experiment to see per-experiment reload costs.
Learn more in the Statsig Warehouse Native docs.
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official release notes from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.