Skip to main content

​
crewship feature-flag

Manage feature flags for the current workspace. The CLI surfaces the override layer (per-workspace on/off) plus a list view that includes the instance default. Flag definitions (creating, renaming, deleting a flag’s identity) are an instance-admin operation and live in the web UI and direct API calls — see the API reference below.
The command accepts the alias crewship flag.

​
Subcommands

​
crewship feature-flag list

Lists every flag the instance knows about with three columns of state plus the resolved effective value:
The global --format flag is honoured (table, json, yaml).

​
crewship feature-flag enable / disable

Writes a per-workspace override. Idempotent — repeating the command is a no-op. The override always wins over the instance default and the rollout percentage, so use these to opt a single workspace into or out of a flag regardless of the broader rollout state.

​
crewship feature-flag inherit

Removes the override. The next read of the flag reverts to the instance default + gradual-rollout percentage logic. Use this when you want a previously-pinned workspace to follow the instance default again.

​
API

The CLI is a thin wrapper over six endpoints: Flag definition CRUD (the three middle rows) intentionally has no CLI wrapper — creating a flag is an instance-admin event that should land via a code change, a migration, or the admin UI rather than an ad-hoc CLI call.

​
Common errors

  • API error (404): Feature flag not found — the <key> you passed doesn’t exist on this instance. Run crewship feature-flag list to see the catalog.
  • API error (403): Forbidden — override writes require OWNER / ADMIN (canRole "manage"). MEMBER and VIEWER roles can only list.

​
See also