Feature flags for AI agents.

What is Flagger.gg?

Flagger.gg is a feature-flag platform built for teams whose code is increasingly written and shipped by AI agents. A feature flag lets you merge and deploy unfinished work switched off, then turn it on for the right people when it's ready. Flagger.gg is designed so an agent can do that work itself, while a person keeps the final say on anything risky.

Jon Oringer, who founded North Bay Ventures, puts it simply: it's a feature flag system for agents, because everything the studio builds is for agents.

Why do agents need their own feature flags?

Coding agents produce more changes, in smaller pieces, more often. Shipping each change switched off behind a flag keeps that pace safe: the deploy is routine, and turning the feature on is a separate, deliberate step. When an agent can create the flag for its own work, turn it on for its team, watch it and roll it back, it can carry a change all the way through without leaving a mess for a person to clean up.

The guardrails matter as much as the speed. Every change records who made it, when, what it was before and after, and why. In auto-live mode (the default today) an agent's new flag goes live straight away unless it's marked not ready. Turning approvals on adds a per-environment cap (10% by default in production) above which a human approves in the console. Agents have no approve tool.

What is it built on?

Flagger.gg is built on the flag system that already runs Sandboxer and Transformer in production. That system has five states, from off for everyone to on for everyone, with steps for admins only, named users and workspaces, and a sticky percentage of users in between. A flag that is unknown or can't be loaded counts as off, and work that isn't finished can be marked not ready so it stays off. Read how that works in feature flags instead of staging.

Teams that already run flags can bring them along: Flagger.gg imports an app's existing flags with their history, and a shadow mode compares its answers with the existing system before the switch.

How do I start using Flagger.gg?

Sign up at app.flagger.gg with an email link or Google. Each account gets its own organization and a project in auto-live mode, with production and development environments. Apps check flags with the Go and Node SDKs, and agents connect through the hosted MCP server at mcp.flagger.gg or the flagger CLI. There is no public pricing.

Some features are still in development, including flags tied to metrics with automatic rollback, experiments, and SDKs beyond Go and Node. The features page and how it works show what is live today.

How does Flagger.gg fit with Sandboxer and Transformer?

All three are built for a world where agents do real work. Sandboxer gives every agent its own computer. Transformer lets agents run creator campaigns. Flagger.gg lets agents ship their changes safely behind feature flags. Each can be used by a person or driven by an agent, and each keeps a person in control of the decisions that are hard to undo.