tinyhumansai/openhuman · error

runtime-node feature disabled at compile time — rebuild with

Error message

runtime-node feature disabled at compile time — rebuild with `--features runtime-node` to use the managed Node.js toolchain

What it means

The stub NodeBootstrap (compiled when the runtime-node Cargo feature is off) always fails resolve() with this build fact. It mirrors the real API so callers need no cfg: try_cached/probe_installed return None and resolve is a permanent error in this binary.

Source

Thrown at src/openhuman/runtime/node/stub.rs:87

            _config: config,
            _workspace_dir: workspace_dir,
        }
    }

    /// Always `None` — nothing is cached because nothing resolves.
    pub fn try_cached(&self) -> Option<ResolvedNode> {
        None
    }

    /// Always `None`. The real implementation probes the on-disk install; there
    /// is no install path in a disabled build.
    pub async fn probe_installed(&self) -> Option<ResolvedNode> {
        None
    }

    /// Always `Err`. See [`RUNTIME_NODE_DISABLED_MESSAGE`].
    pub async fn resolve(&self) -> Result<ResolvedNode> {
        anyhow::bail!(RUNTIME_NODE_DISABLED_MESSAGE)
    }
}

View on GitHub (pinned to 7491200858)

Solutions

1. Rebuild the core with --features runtime-node (the product desktop build enables it)
2. Run a build that ships the managed toolchain instead of a slim one

When it happens

Trigger: Thrown at src/openhuman/runtime/node/stub.rs:87 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of tinyhumansai/openhuman@7491200858 (2026-08-17). Data as JSON: /api/errors/5001766217e20808. Report an issue: GitHub.