What causes "The --conversation flag is not available in this build" in warpdotdev/warp?

Drop `--conversation` and use plain `warp task get ` for status output

The --conversation flag is not available in this build

Error message

The --conversation flag is not available in this build

What it means

The `--conversation` flag on `warp task get` is gated behind the ConversationApi feature flag. On builds where the flag is off, the flag is rejected before any server call, failing fast instead of hitting an unsupported conversation API.

Source

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

                return Err(AgentDriverError::AIWorkflowNotFound(workflow_id.to_owned()));
            };
            Ok(query.to_owned())
        }
    }
}

/// Run the task with the provided command.
fn run_task(
    ctx: &mut AppContext,
    global_options: GlobalOptions,
    command: TaskCommand,
) -> anyhow::Result<()> {
    match command {
        TaskCommand::List(args) => ambient::list_ambient_agent_tasks(ctx, global_options, args),
        TaskCommand::Get(args) => {
            if args.conversation {
                if !FeatureFlag::ConversationApi.is_enabled() {
                    return Err(anyhow::anyhow!(
                        "The --conversation flag is not available in this build"
                    ));
                }
                ambient::get_run_conversation(ctx, args.task_id)
            } else {
                ambient::get_ambient_agent_task_status(ctx, global_options, args)
            }
        }
        TaskCommand::Conversation(conv_cmd) => {
            if !FeatureFlag::ConversationApi.is_enabled() {
                return Err(anyhow::anyhow!(
                    "The 'conversation' subcommand is not available in this build"
                ));
            }
            match conv_cmd {
                warp_cli::task::ConversationCommand::Get(args) => {
                    ambient::get_conversation(ctx, args.conversation_id)
                }

View on GitHub (pinned to e72fd7aacb)

Solutions

Drop `--conversation` and use plain `warp task get <task_id>` for status output
Run on a build/channel where ConversationApi is enabled (dogfood/preview)
Pin CI scripts to a CLI version whose flag set matches the script

Example fix

# before
warp task get --conversation abc123

# after
warp task get abc123   # or use a dogfood build with ConversationApi enabled

Defensive patterns

Strategy: validation

Validate before calling

# Probe the build once; fall back to the flag-free form when unavailable
out=$(warp task get --conversation "$TASK_ID" 2>&1) || \
  case "$out" in *'not available in this build'*) warp task get "$TASK_ID";; *) echo "$out" >&2; exit 1;; esac

Try / catch

out=$(warp task get --conversation "$id" 2>&1) || { case "$out" in *'--conversation flag is not available'*) warp task get "$id";; *) echo "$out" >&2; exit 1;; esac; }

Prevention

Pin script CLI versions and test flags against that exact build
Prefer the flag-free command when the extra data is optional
Track which feature flags each channel enables before scripting gated flags

When it happens

Trigger: `warp task get --conversation <task_id>` on a build where `FeatureFlag::ConversationApi.is_enabled()` is false.

Common situations: Scripts written against a dogfood build (flag enabled) then run on stable; documentation or tutorials that predate flag rollout; version skew between a pinned CI CLI and the script's assumptions.

Related errors

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