Add a Studio feature flag

Studio flags live in web/packages/studio and are wired into the FastAPI Studio bundle via marker replacement at runtime. Follow every step that applies so local dev, FastAPI builds, and cluster deploys stay consistent.

For broader Studio context, see [.cursor/skills/studio-dev/SKILL.md](../studio-dev/SKILL.md).

1. Choose flag shape

Preview behavior: true and 'preview' are both truthy for if (featureFlags.myFlag). Only 'preview' triggers FeatureFlagBadge (see step 6).

Naming

• Env var: VITEFF<SCREAMINGSNAKECASE>
• flagDefinitions key: camelCase (e.g. jobQueueEnabled)
• studio.featureflags / configpath: snakecase (e.g. jobqueue_enabled)

2. Register the flag (TypeScript)

File: web/packages/studio/src/constants/featureFlags/featureFlags.ts

Add one entry to flagDefinitions:

jobQueueEnabled: previewFlag('VITE_FF_JOB_QUEUE_ENABLED'),
// or
jobQueueEnabled: booleanFlag('VITE_FF_JOB_QUEUE_ENABLED'),

Alphabetical order with sibling keys is preferred.

Consume

import { featureFlags } from "@studio/constants/featureFlags";

if (featureFlags.jobQueueEnabled) {
  // enabled (true or 'preview')
}

3. Optional: environment.ts re-export

File: web/packages/studio/src/constants/environment.ts

If the codebase prefers SOMEFEATUREENABLED constants (see existing MEMBERSENABLED, SECRETSENABLED, etc.), add:

export const JOB_QUEUE_ENABLED = featureFlags.jobQueueEnabled !== false;

Use this only when it matches an established pattern for that area of the app.

4. Runtime injection (FastAPI Studio service)

File: services/studio/src/nmp/studio/env_mappings.py

Add an EnvMapping in ENV_MAPPINGS (keep the feature-flag block grouped):

EnvMapping(
    marker="STUDIO_UI_VITE_FF_JOB_QUEUE_ENABLED",
    config_path="studio.feature_flags.job_queue_enabled",
    default="false",
),

• marker is always STUDIOUI + the Vite env name (VITEFF...).
• default is a string ("true", "false", or "preview" for preview flags).

5. FastAPI build env markers (parity)

File: web/packages/studio/env/.env.fastapi

Add a line so the built bundle contains the placeholder the Studio service replaces:

VITE_FF_JOB_QUEUE_ENABLED=STUDIO_UI_VITE_FF_JOB_QUEUE_ENABLED

The file header requires parity with env_mappings.py—do not skip this for flags used in FastAPI mode.

6. Local development

Update both files so the sample stays in lockstep with the feature-flag inventory — devs copy the sample to bootstrap .env.dev.local, and a missing entry means the flag silently falls back to its default.

File: web/packages/studio/env/.env.dev.local.sample (always — committed reference)

Add the flag in the # Feature Flags (VITEFF prefix) block, alphabetized with sibling VITEFF lines. Use the value a new developer should start with (usually the same as the default in env_mappings.py):

VITE_FF_JOB_QUEUE_ENABLED='false'

File: web/packages/studio/env/.env.dev.local (only if you want it on for your own machine — gitignored)

VITE_FF_JOB_QUEUE_ENABLED='true'
# or for preview badge behavior:
VITE_FF_JOB_QUEUE_ENABLED='preview'

7. Gate UI and routes

• Routes: lazy imports / children arrays in web/packages/studio/src/routes/index.tsx, or conditional wrappers—mirror existing flags (e.g. membersEnabled, secretsEnabled).
• Nav: WorkspaceSideNav and similar—search for featureFlags. patterns.
• Preview badge: For previewFlag entries, add <FeatureFlagBadge flag="jobQueueEnabled" /> next to the feature title when appropriate (web/packages/studio/src/components/FeatureFlagBadge/index.tsx).

8. Helm / platform config (deployed environments)

Under studio.featureflags in values (e.g. deploy/helm/values/ci/dev-values.yaml), add the snakecase key with string value true, false, or preview as needed.

Global settings schema may need updating if the new key is not yet defined—follow how existing studio.feature_flags.* keys are declared in the repo.

Checklist

Copy and track:

• flagDefinitions in featureFlags.ts (correct helper + defaults)
• EnvMapping in env_mappings.py
• VITEFF=STUDIOUIVITEFF line in env/.env.fastapi
• env/.env.dev.local.sample updated (committed reference for new devs)
• Local env/.env.dev.local (only if developers need the flag on for their own machine)
• UI/route/nav gated with featureFlags.<key> or environment.ts constant
• FeatureFlagBadge if the flag uses previewFlag and should show Early Preview
• Helm / values or docs updated for environments that should see the flag
• pnpm typecheck (from web/packages/studio or monorepo Studio package) after TS edits

Removing a flag (reference)

1. Remove all usages.
2. Remove from flagDefinitions, env_mappings.py, .env.fastapi, Helm values, and samples.
3. Remove any environment.ts export.