It’s estimated that over 40% of all new code is now written by AI and that trend is likely to accelerate, leading to an exponential increase in the total code being shipped to production. This is not necessarily a net benefit for companies though—who’s to say the extra code is actually helping the business? In the early 2000s, Yahoo added exponentially more widgets to their homepage, while Google kept things simple and we all know how that turned out.
Industry-wide, only about a third of product changes actually have a positive impact on a company’s core business metrics. The rest either do nothing to move the needle or can even be unintentionally harmful. Without proper measurement and safeguards, you could be vibe coding your way to a product no one wants to use.
This is not a new problem, and there is already an established solution from the pre-AI days. Feature flags and experiments have been used by all of the top companies for years to measure code changes in production and ship the ones that work while reverting the ones that don’t.
In this new vibe coding paradigm, feature flags are still the right way to release code, and experimentation is still the right way to measure impact and make the ship/revert decision. The solution is the same, but the scale of the problem is increasing exponentially.
The good news is that GrowthBook, the most popular open source feature flag and experimentation platform, just launched 2 products tailored specifically for this new reality.
First are Safe Rollouts, which are super lightweight experiments that require much less developer involvement to set up and manage. Safe Rollouts gradually ramp up traffic to a feature while monitoring key guardrail metrics for regressions. If anything goes wrong, it can automatically revert the change and alert you. The goal is to make sure safety and experimentation don’t get in the way of increased velocity.
Second, we released the first-ever MCP Server for feature management and experimentation! Developers can now create feature flags, configure Safe Rollouts, monitor results, and more—all without ever leaving their IDE. This makes it trivially easy for developers to incorporate GrowthBook into their AI-driven development workflow.
This is one of the first real glimpses of what AI + developer tools can look like when they actually work together. We’re just getting started.
Read more about the GrowthBook MCP Server.
