native session bridge warm command failed with status {}

Error message

native session bridge warm command failed with status {}

What it means

Flow can warm a native (non-JD) session bridge by running a warm command as a child process. When that command exits with a non-zero status, the function rolls back the previously recorded warm-state timestamp (so a later retry isn't skipped due to a stale success stamp) and bails with the child's exit status embedded in the message.

Source

Thrown at src/ai.rs:9043

        .arg("warm-recent")
        .arg("--limit")
        .arg(jd_session_bridge_warm_limit().to_string())
        .arg("--count")
        .arg(jd_session_bridge_warm_count().to_string())
        .stdin(Stdio::null())
        .stdout(Stdio::null())
        .stderr(Stdio::null())
        .status()
        .with_context(|| format!("failed to run {}", tool_path.display()))?;

    if status.success() {
        Ok(1)
    } else {
        let mut guard = jd_session_bridge_warm_state()
            .lock()
            .expect("jd session bridge warm mutex poisoned");
        *guard = previous_stamp;
        bail!(
            "native session bridge warm command failed with status {}",
            status
        );
    }
}

fn codex_eval_commands(target_path: &Path) -> Vec<CodexEvalCommand> {
    let target = target_path.display().to_string();
    vec![
        CodexEvalCommand {
            label: "Doctor".to_string(),
            command: format!("f codex doctor --path {}", target),
        },
        CodexEvalCommand {
            label: "Autonomous readiness".to_string(),
            command: format!("f codex doctor --path {} --assert-autonomous", target),
        },
        CodexEvalCommand {

View on GitHub (pinned to a747e741ae)

Solutions

Re-run the warm command after checking the reported exit status; the state rollback means it will actually retry
Verify the native session-bridge binary is installed, on PATH, and executable
Check daemon/bridge logs for the underlying failure that produced the non-zero exit
Repair or reinstall the bridge (reinstall Flow's native components or run the project's setup/doctor command)

Example fix

// before
error: native session bridge warm command failed with status 101
// after
$ which f-bridge && f-bridge --version   # confirm bridge installed
$ f codex doctor                          # or reinstall native components
$ <warm command>                          # retry; status stamp was rolled back

Defensive patterns

Strategy: retry

Validate before calling

// Shell: verify the bridge binary exists before warming
command -v f-bridge >/dev/null 2>&1 || { echo "bridge not installed"; exit 1; }

Type guard

fn warm_succeeded(status: std::process::ExitStatus) -> bool {
    status.success()
}

Try / catch

// Rust: retry warm with backoff since state stamp is rolled back on failure
for attempt in 0..3 {
    match warm_session_bridge() {
        Ok(()) => break,
        Err(e) if e.to_string().contains("warm command failed with status") => {
            eprintln!("warm failed ({e}), retrying ({attempt})");
            std::thread::sleep(Duration::from_secs(2u64.pow(attempt)));
        }
        Err(e) => return Err(e),
    }
}

Prevention

Keep the native bridge components installed and updated together with Flow
Check the exit status in the message and consult bridge logs for the root cause
Retry after failures — the warm-state timestamp is rolled back so retries are not skipped

When it happens

Trigger: Invoking the session-bridge warm flow where the underlying native warm command exits with a failing status code (any non-zero status) — e.g. the bridge binary is missing, crashes, or reports an initialization failure.

Common situations: Native bridge binary not installed or on PATH after an update; corrupted bridge state causing the warm command to fail; transient daemon/session-bridge startup crashes; running warm from an environment where the bridge cannot initialize (permissions, missing env).

Related errors

AI-assisted analysis of nikivdev/code@a747e741ae (2026-09-01). Data as JSON: /api/errors/d67afbce2e8f55c5. Report an issue: GitHub.