zeroclaw-labs/zeroclaw · error
cli-alias-not-configured
cli-alias-not-configured
Error message
{$path} is not configured What it means
Error "{$path} is not configured" thrown in zeroclaw-labs/zeroclaw.
Source
Thrown at src/alias_cli/mod.rs:269
"{}",
mta(
"cli-alias-delete-refused-header",
&[("count", count.as_str())],
"refused: {$count} hard reference(s) block the delete:"
)
);
for b in &report.blockers {
println!(" ✗ {}", b.path);
}
bail!(
"{}",
mt(
"cli-alias-delete-refused-hint",
"delete refused — resolve the hard references first"
)
);
}
Err(CascadeError::NotFound(p)) => bail!(
"{}",
mta(
"cli-alias-not-configured",
&[("path", p.as_str())],
"{$path} is not configured"
)
),
Err(e) => {
let es = e.to_string();
bail!(
"{}",
mta(
"cli-alias-delete-failed",
&[("error", es.as_str())],
"delete failed: {$error}"
)
)
}View on GitHub (pinned to 88bb9c8533)
Solutions
- Configure the path first with `zeroclaw config set <path> <value>`, then retry the operation.
- Check the path spelling against existing keys shown by `zeroclaw config get`.
When it happens
Trigger: Thrown at src/alias_cli/mod.rs:269 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/ec2415efd58112a2.
Report an issue: GitHub.