warpdotdev/warp · error · anyhow::Error

This feature is not enabled

Error message

This feature is not enabled

What it means

The whole oz secret command group is gated on the runtime feature flag WarpManagedSecrets. secret::run checks the flag before dispatching to any subcommand and returns this generic error when the flag is disabled for the current build, user, or rollout cohort. Nothing is wrong with the arguments; the feature simply is not switched on.

Source

Thrown at app/src/ai/agent_sdk/secret.rs:71

    fn row(&self) -> Vec<Cell> {
        vec![
            Cell::new(&self.name),
            Cell::new(&self.scope),
            Cell::new(format_secret_type(&self.secret_type)),
            Cell::new(format_approx_duration_from_now_utc(self.created_at)),
            Cell::new(format_approx_duration_from_now_utc(self.updated_at)),
        ]
    }
}

/// Run secret-related commands.
pub fn run(
    ctx: &mut AppContext,
    global_options: GlobalOptions,
    command: SecretCommand,
) -> Result<()> {
    if !FeatureFlag::WarpManagedSecrets.is_enabled() {
        return Err(anyhow::anyhow!("This feature is not enabled"));
    }

    match command {
        SecretCommand::Create(args) => create_secret(ctx, args),
        SecretCommand::Delete(args) => delete_secret(ctx, args),
        SecretCommand::Update(args) => update_secret(ctx, args),
        SecretCommand::List(args) => list_secrets(ctx, global_options.output_format, args),
    }
}

/// Deferred secret value reader. Constructed during argument parsing but read after validation
/// (refresh metadata, resolve owner) so users are not prompted for secrets before we know the
/// request is valid.
enum SecretInput {
    /// Single-field secret types (raw value, Anthropic API key).
    Simple {
        secret_type: SecretType,
        value_args: ValueArgs,

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Run the command from a build/channel where WarpManagedSecrets is enabled (dogfood or preview rollout)
2. Check the feature-flag surface for the current user/build before scripting secret commands
3. If you own the rollout, enable WarpManagedSecrets for this user/cohort and retry

Example fix

// before
#!/bin/sh
oz secret list
# Error: This feature is not enabled

// after
#!/bin/sh
oz features get WarpManagedSecrets | grep -q true || { echo 'secrets unavailable'; exit 1; }
oz secret list

if !FeatureFlag::WarpManagedSecrets.is_enabled() {
    anyhow::bail!("WarpManagedSecrets is disabled here; skipping secret commands");
}
secret::run(ctx, global_options, command)?;

When it happens

Trigger: Any oz secret ... invocation (create/delete/update/list) on a build or account where WarpManagedSecrets is disabled, e.g. a stable build without the rollout or a flag rolled back server-side.

Common situations: Scripts written against a dogfood build run on stable; local dev build without the flag; feature disabled by admin policy; preview flag removed before release.

Related errors

• `runner_id` is set in the config file but runner support is
• Secret name is required. Usage: oz secret create <NAME>
• Refusing to delete secret without confirmation in non-intera
• Secret '{}' not found
• Bedrock access key secrets cannot be updated via `--value`;

AI-assisted analysis of warpdotdev/warp@e72fd7aacb (2026-08-16). Data as JSON: /api/errors/bbbe214399142295. Report an issue: GitHub.