Create and edit with Statbot
Ask Statbot to propose a Statsig configuration change, inspect the proposal, and confirm a direct change or review request.
This feature is in Early Access. During this time, aspects of the functionality may still be developed, and this documentation may not always be up to date. If you have any questions, contact Statsig Support.
Describe a configuration change in Statbot to receive a proposal you can inspect before confirming. Statbot can propose changes to feature gates, experiments, and dynamic configs, subject to your project permissions. Use the Console's resource editor when you want to configure a resource directly.
Prerequisites
- Enable Statbot for your project.
- Obtain MCP read and write access and permission to create or edit the relevant resource type.
Request a change
- Open Statbot in the project you want to change.
- Describe the resource and intended change. Include its exact name or ID, values, targeting, and environment where relevant.
- Answer any clarification questions. Statbot can ask for required fields such as a team, Target App, or ID type.
- Inspect the proposal before confirming it.
For example, ask Statbot:
- "Create a feature gate named
checkout_refreshand roll it out to 10% of users." - "Create a dynamic config named
homepage_preferenceswithmax_itemsset to10andshow_bannerset tofalse." - "Change the Treatment group's
button_colorparameter incheckout_cta_colortopurple."
Creation and rollout are separate resource operations. Check each proposal to understand which action it performs and confirm any additional proposals needed to complete your request.
Review the proposal
Check the resource, proposed fields, and effect described on the card. Expand the proposal details to inspect the values Statbot intends to send.
- Select Confirm to authorize the action described on the card. Older cards use Accept.
- Select Submit for review when the card proposes opening a review request.
- Select Modify to revise the request before confirming a new proposal.
- Select Cancel to decline the proposal.
Statbot checks your permissions again when applying a confirmed proposal. Confirmation doesn't grant additional permissions or bypass required reviews.
Understand review-required changes
When your project's policy requires a review, Statbot proposes a review request instead of a direct change. Confirming that proposal submits the request; it doesn't make the configuration change live.
Open the review request in the Console to inspect the proposed changes and complete the required reviewer approval and commit steps. Approving a review and committing its changes are separate actions. For policy configuration, go to Setting up Reviews for Team Workflows.
If the resource already has a pending review, resolve that review in the Console or ask Statbot about the existing request before proposing another direct edit. Review operations depend on the resource type and your permissions.
Verify the outcome
After confirming a proposal, check its result in the chat and open the resource in the Console. Verify the saved values or the pending review, including the target environment.
An uncertain outcome needs verification
If Statbot can't confirm whether an action succeeded, inspect the resource or its change history before repeating the request. A timeout doesn't prove that the action failed.
Resolve a blocked or failed action
| Outcome | Next step |
|---|---|
| Statbot lacks write access. | Ask an administrator to check MCP and resource permissions. A permission-blocked draft hasn't changed the resource and isn't an approval. |
| The proposal expired. | Ask Statbot to propose the change again, then inspect and confirm the new proposal. |
| A required field or value is invalid. | Correct the value or answer the clarification question, then inspect the replacement proposal. |
| The action failed with a definite error. | Resolve the reported error before requesting another proposal. |
| The action's outcome is unknown. | Check the resource and change history before trying again. |
After an administrator enables access, ask Statbot to try again. Permission changes don't apply an earlier draft automatically.
Was this helpful?
For AI agents: a documentation index is available at /llms.txt. Append .md to any page URL for markdown, or send Accept: text/markdown.