Hmbown/CodeWhale · error
Cannot resolve current binary path: {e}
Error message
Cannot resolve current binary path: {e} What it means
Error "Cannot resolve current binary path: {e}" thrown in Hmbown/CodeWhale.
Source
Thrown at crates/tui/src/lib.rs:8668
let mut pool = McpPool::from_config_path_with_workspace_and_plugins(
&config_path,
workspace,
std::sync::Arc::new(plugins.clone()),
)?;
let errors = pool.connect_all().await;
if errors.is_empty() {
println!("MCP config is valid. All enabled servers connected.");
return Ok(());
}
eprintln!("MCP validation failed:");
for (name, err) in errors {
eprintln!(" - {name}: {err:#}");
}
bail!("one or more MCP servers failed validation");
}
McpCommand::AddSelf { name, workspace } => {
let exe_path = std::env::current_exe()
.map_err(|e| anyhow!("Cannot resolve current binary path: {e}"))?;
let exe_str = exe_path.to_string_lossy().to_string();
let mut args = vec!["serve".to_string(), "--mcp".to_string()];
if let Some(ref ws) = workspace {
args.push("--workspace".to_string());
args.push(ws.clone());
}
let mut cfg = load_mcp_config(&config_path)?;
if cfg.servers.contains_key(&name) {
bail!(
"MCP server '{name}' already exists in {}. Use `codewhale mcp remove {name}` first, or choose a different --name.",
config_path.display()
);
}
cfg.servers.insert(
name.clone(),
McpServerConfig {View on GitHub (pinned to 8880682c63)
When it happens
Trigger: Thrown at crates/tui/src/lib.rs:8668 when the library encounters an invalid state.
Common situations: See trigger scenarios.
AI-assisted analysis of Hmbown/CodeWhale@8880682c63 (2026-08-16).
Data as JSON: /api/errors/94cf18be5ecc8fbf.
Report an issue: GitHub.