You can now submit Autotune changes for review and manage the full review lifecycle across the console, Console API, and MCP.
Submit Autotune configuration changes for review before they reach production.
Approve, reject, or cancel in-flight Autotune reviews from the console, via CAPI, or through the MCP.
Teams with reviews required can now enforce that same approval workflow on Autotunes, the same way they do for gates and experiments.
Teams running Autotune for high-stakes decisions need the same guardrails they have everywhere else. Any change to a live Autotune can shift traffic allocation immediately, so being able to require an approval before it goes out matters. Reviews are now consistent across gates, experiments, and Autotunes.
If you have the Statsig MCP set up, try a prompt like:
"Using the Statsig MCP, open a review to update the winner threshold on
autotune_nameand submit it for approval."
Learn more in the Statsig Reviews docs.