tinyhumansai/openhuman · error
Rust-native browser backend is not compiled. Rebuild with --
Error message
Rust-native browser backend is not compiled. Rebuild with --features browser-native
What it means
The rust-native action execution path was reached in a binary compiled without the 'browser-native' feature (the cfg(not) stub). Unlike resolve_backend, which gates earlier, this fires if execution still selects the rust-native path; the fix is a rebuild.
Source
Thrown at src/openhuman/tools/impl/browser/browser.rs:523
let output = state
.execute_action(
action,
self.native_headless,
&self.native_webdriver_url,
self.native_chrome_path.as_deref(),
)
.await?;
Ok(ToolResult::success(
serde_json::to_string_pretty(&output).unwrap_or_default(),
))
}
#[cfg(not(feature = "browser-native"))]
{
let _ = action;
anyhow::bail!(
"Rust-native browser backend is not compiled. Rebuild with --features browser-native"
)
}
}
async fn execute_playwright_action(&self, action: BrowserAction) -> anyhow::Result<ToolResult> {
if let BrowserAction::Open { url } = &action {
debug!("[browser] validating playwright open url before dispatch");
self.validate_url(url)?;
}
let mut state = self.playwright_state.lock().await;
let output = state
.execute_action(
action,
self.native_headless,
Some(playwright_backend::BrowserUrlPolicy {
allowed_domains: self.allowed_domains.clone(),View on GitHub (pinned to 7491200858)
Solutions
- Rebuild the core with --features browser-native.
- Route the action through an available backend (playwright, agent-browser, computer_use).
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at src/openhuman/tools/impl/browser/browser.rs:523 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/b937111057b155fb.
Report an issue: GitHub.