warpdotdev/warp · error

Unsupported feature

Error message

Unsupported feature

What it means

run_agent for ambient/cloud agents (app/src/ai/agent_sdk/ambient.rs:235) is gated behind FeatureFlag::AmbientAgentsCommandLine; when the flag is disabled for the build/account, the command returns this generic anyhow error before doing any setup work. Feature flags are runtime-plumbed (server-configured rollout plus build defaults), so availability varies by channel and account.

Source

Thrown at app/src/ai/agent_sdk/ambient.rs:235

impl AmbientAgentRunner {
    fn spawn_command(
        &self,
        future: impl Spawnable<Output = anyhow::Result<()>>,
        ctx: &mut ModelContext<Self>,
    ) {
        ctx.spawn(future, |_, result, ctx| match result {
            Ok(()) => {
                ctx.terminate_app(TerminationMode::ForceTerminate, None);
            }
            Err(err) => {
                super::report_fatal_error(err, ctx);
            }
        });
    }
    fn run_agent(&self, args: RunCloudArgs, ctx: &mut ModelContext<Self>) -> anyhow::Result<()> {
        if !FeatureFlag::AmbientAgentsCommandLine.is_enabled() {
            return Err(anyhow::anyhow!("Unsupported feature"));
        }
        let skill_enabled = FeatureFlag::OzPlatformSkills.is_enabled();
        if args.skill.is_some() && !skill_enabled {
            return Err(anyhow::anyhow!("unexpected argument '--skill' found"));
        }

        let refresh_future = super::common::refresh_workspace_metadata(ctx);
        let warp_drive_sync_future = super::common::refresh_warp_drive(ctx);
        let setup_future = future::try_join(refresh_future, warp_drive_sync_future);

        ctx.spawn(setup_future, move |_runner, setup_result, ctx| {
            if let Err(err) = setup_result {
                super::report_fatal_error(err, ctx);
                return;
            }

            // Validate that at least one of prompt, skill, or conversation is provided.
            // conversation is used to continue an existing cloud conversation.

View on GitHub (pinned to e72fd7aacb)

Solutions

1. Check FeatureFlag::AmbientAgentsCommandLine.is_enabled() for your build/account before relying on the command
2. Use a build/channel where the flag is enabled (dogfood or preview)
3. Wait for rollout or request enablement for the account

if !FeatureFlag::AmbientAgentsCommandLine.is_enabled() {
    // hide/disable the ambient-agents command in wrappers and scripts
}

fn ambient_agent_cli_available() -> bool {
    FeatureFlag::AmbientAgentsCommandLine.is_enabled()
}

When it happens

Trigger: Invoking the ambient-agents/cloud run command on a build or account where AmbientAgentsCommandLine is not enabled (e.g. stable channel before rollout, or a post-launch removal).

Common situations: Trying a preview feature on stable; flag disabled server-side for the account/team; flag removed after the feature graduated.

Related errors

• unexpected argument '--skill' found
• Either --prompt, --skill, or --conversation must be provided
• Attachment upload is not enabled
• The --conversation flag is not available in this build
• The 'conversation' subcommand is not available in this build

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