Feature Flags Panel
An environment chip row above flag rows with a mono key, rollout meter, kind badge, last editor avatar, and an enable switch.
An environment chip row above flag rows with a mono key, rollout meter, kind badge, last editor avatar, and an enable switch.
The source for every Application block is included with Basic and Pro. Pick a plan to copy the code.
Already purchased? Log in
Feature Flags Panel is the flag management surface for the acme-app project, evaluated at the edge. An environment chip row sets the scope to Production, Staging, or Development, with a note that the values shown are for Production. Below it, five flag rows each carry a monospace key, a one line description, a kind Badge that reads on/off, percentage, or targeted, a rollout meter with a percent readout, the last editor avatar with a relative timestamp, and an enable Switch. The onboarding.legacy_tour flag is stale: it wears a stale Badge and a nudge that it has had no evaluations in 30 days, suggesting an archive.
Flags are one typed const array and kindLabel is a Record, so each kind maps to a plain word without extra branching. The stale entry drives both the muted key and the archive line from a single boolean, and the footer records that toggles propagate to SDK clients within 30 seconds and land in the audit log with actor and previous value.
Reach for this block on the project settings or feature management page, wired to your flag provider and scoped to the selected environment. Point the Switch at your toggle endpoint and confirm the change reaches connected SDK clients before you close the panel.
A natural flow around it on an Application Pro page:
Before
After
One strong use is the environment scoped flag list. Other flag surfaces:
Tip: the stale nudge is the housekeeping cue; surfacing the 30 day evaluation gap in the row is what gets dead flags archived instead of forgotten.