warpdotdev/warp · error

invalid value 'federate'

Error message

invalid value 'federate'

What it means

Thrown by the dispatcher arm for CliCommand::Federate (mod.rs:196) when `federate` parsed but FeatureFlag::OzIdentityFederation is disabled. The clap-style 'invalid value' error makes the identity-federation subcommand invisible when the flag is off. Flag defaults to false; not in the always-on lists, so it depends on launch environment/server enrollment.

Source

Thrown at app/src/ai/agent_sdk/mod.rs:196

        #[cfg(target_family = "wasm")]
        CliCommand::Integration(_) => {
            return Err(anyhow::anyhow!("invalid value 'integration'"));
        }
        CliCommand::Schedule(schedule_cmd) => {
            if !FeatureFlag::ScheduledAmbientAgents.is_enabled() {
                return Err(anyhow::anyhow!("invalid value 'schedule'"));
            }
            schedule::run(ctx, global_options, schedule_cmd)
        }
        CliCommand::Secret(secret_cmd) => {
            if !FeatureFlag::WarpManagedSecrets.is_enabled() {
                return Err(anyhow::anyhow!("invalid value 'secret'"));
            }
            secret::run(ctx, global_options, secret_cmd)
        }
        CliCommand::Federate(federate_cmd) => {
            if !FeatureFlag::OzIdentityFederation.is_enabled() {
                return Err(anyhow::anyhow!("invalid value 'federate'"));
            }
            federate::run(ctx, global_options, federate_cmd)
        }
        CliCommand::HarnessSupport(args) => {
            if !FeatureFlag::AgentHarness.is_enabled() {
                return Err(anyhow::anyhow!("invalid value 'harness-support'"));
            }
            harness_support::run(ctx, global_options, args)
        }
        CliCommand::Artifact(artifact_cmd) => {
            if !FeatureFlag::ArtifactCommand.is_enabled() {
                return Err(anyhow::anyhow!("invalid value 'artifact'"));
            }
            artifact::run(ctx, global_options, artifact_cmd)
        }
        CliCommand::ApiKey(api_key_cmd) => {
            if !FeatureFlag::APIKeyManagement.is_enabled() {
                return Err(anyhow::anyhow!("invalid value 'api-key'"));

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Use a build/account where OzIdentityFederation is enabled; federation is typically rolled out org-by-org
2. Verify your CLI version and org enrollment, then update the CLI if federation shipped after your build
3. As a Warp developer, override the flag or add it to DOGFOOD_FLAGS and rebuild
4. If federation is not intended, remove the `federate` step from the workflow

Example fix

# before
$ oz federate status
Error: invalid value 'federate'

# after (probe once, fail with context)
anyhow::ensure!(
    FeatureFlag::OzIdentityFederation.is_enabled(),
    "identity federation is not enabled for this account/build"
);

if matches!(cmd, CliCommand::Federate(_))
    && !FeatureFlag::OzIdentityFederation.is_enabled()
{
    return Ok(());
}

pub fn federate_cmd_available() -> bool {
    FeatureFlag::OzIdentityFederation.is_enabled()
}

match agent_sdk::run(ctx, opts, cmd) {
    Err(e) if e.to_string() == "invalid value 'federate'" => {
        // federation not enabled for this org/build; surface to admin
    }
    result => result?,
}

When it happens

Trigger: Invoking `<cli> federate <subcmd>` (identity/SSO federation operations) where FeatureFlag::OzIdentityFederation.is_enabled() == false.

Common situations: Enterprise/SSO setup automation run against a build without the federation rollout; org tenant not yet enrolled; CLI version newer or older than the server's federation support.

Related errors

• invalid value 'integration'
• invalid value 'schedule'
• invalid value 'secret'
• invalid value 'harness-support'
• invalid value 'artifact'

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