zeroclaw-labs/zeroclaw · error
cli-alias-no-such-section
cli-alias-no-such-section
Error message
no such config section: {$section} What it means
Error "no such config section: {$section}" thrown in zeroclaw-labs/zeroclaw.
Source
Thrown at src/alias_cli/mod.rs:91
match config.get_map_keys(section) {
Some(mut keys) => {
keys.sort();
if keys.is_empty() {
println!(
"{}",
mta(
"cli-alias-list-empty",
&[("section", section)],
"(no entries under {$section})"
)
);
} else {
for k in keys {
println!("{k}");
}
}
}
None => bail!(
"{}",
mta(
"cli-alias-no-such-section",
&[("section", section)],
"no such config section: {$section}"
)
),
}
Ok(())
}
fn create_entry(config: &mut Config, section: &str, alias: &str) -> Result<()> {
// Shared guarded boundary: refuses the reserved `default` agent here too (an
// operator create surface), and delegates unchanged for every other section.
// The Reserved rejection is localized via Fluent like the delete/rename guards
// below; Invalid (unknown section) keeps its pre-existing bare error.
let created = match alias_refs::create_map_key_checked(config, section, alias) {
Ok(created) => created,View on GitHub (pinned to 88bb9c8533)
Solutions
- Check the section name against `zeroclaw config get` output and use an existing config section.
- Create the section first with `zeroclaw config set <section>.<key> <value>` before aliasing it.
When it happens
Trigger: Thrown at src/alias_cli/mod.rs:91 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/05736865197de7f0.
Report an issue: GitHub.