zeroclaw-labs/zeroclaw · error · anyhow::Error
{e}
Error message
{e} What it means
Error "{e}" thrown in zeroclaw-labs/zeroclaw.
Source
Thrown at src/main.rs:5536
} else {
println!("{value}");
}
}
Err(e) => {
// Classify the anyhow string into a stable code so
// the CLI's --json envelope matches the HTTP shape.
// Same single-source-of-truth helper the gateway
// uses; never hardcode a code at the call site.
let api_err =
zeroclaw_config::api_error::ConfigApiError::from_validation(
anyhow::Error::msg(e.to_string()),
)
.with_path(&path);
if json {
eprintln!("{}", serde_json::to_string_pretty(&api_err)?);
std::process::exit(1);
}
anyhow::bail!("{e}");
}
}
}
Ok(())
}
ConfigCommands::Set {
path,
value,
no_interactive,
comment,
json,
} => {
crate::config::migration::ensure_disk_at_current_version(&config.config_path)?;
let known_paths: Vec<String> =
config.prop_fields().into_iter().map(|f| f.name).collect();
let mut path = zeroclaw_config::helpers::resolve_field_path(&known_paths, &path);
if ensure_map_key_for_prop_path(&mut config, &path)? {
let known_paths: Vec<String> =View on GitHub (pinned to 88bb9c8533)
Solutions
- Read the wrapped error message, address the underlying cause it describes, and retry the command.
- Re-run with verbose logging (RUST_LOG=debug) to get more context on the failure.
When it happens
Trigger: Thrown at src/main.rs:5536 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of zeroclaw-labs/zeroclaw@88bb9c8533 (2026-08-23).
Data as JSON: /api/errors/f601a89e3462ad51.
Report an issue: GitHub.