zeroclaw-labs/zeroclaw · error
cli-alias-delete-reserved-default
cli-alias-delete-reserved-default
Error message
the `default` agent is reserved and cannot be deleted
What it means
Error "the `default` agent is reserved and cannot be deleted" thrown in zeroclaw-labs/zeroclaw.
Source
Thrown at src/alias_cli/mod.rs:382
}
AgentsCommands::Rename { from, to } => {
// Capture the workspace path while the `from` entry still exists
// (custom paths are read off the entry, which the rename moves).
let old_ws = config.agent_workspace_dir(&from);
rename_config(config, &AliasKind::Agent, &from, &to)?;
// Persist the config rename before the irreversible owned-state side
// effects (workspace move + DB re-point), so a later failure can't
// leave the config and owned state split.
save(config).await?;
agent_rename_owned_state(config, &from, &to, &old_ws).await
}
AgentsCommands::Delete {
alias,
dry_run,
yes,
} => {
if alias_refs::is_reserved_agent_alias(&alias) {
bail!(
"{}",
mt(
"cli-alias-delete-reserved-default",
"the `default` agent is reserved and cannot be deleted"
)
);
}
if dry_run {
print_impact(&AliasKind::Agent, &alias, config);
return Ok(());
}
if !yes {
print_impact(&AliasKind::Agent, &alias, config);
println!(
"\n{}",
mt(
"cli-alias-no-changes",
"No changes made. Re-run with --yes to apply (or --dry-run to preview)."View on GitHub (pinned to 88bb9c8533)
Solutions
- The `default` agent cannot be deleted; delete a different agent or reset the default agent's configuration instead.
- Remove the custom agents and keep `default`, or edit config.toml to clear unwanted default settings.
When it happens
Trigger: Thrown at src/alias_cli/mod.rs:382 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/a6e163d867dc3ae8.
Report an issue: GitHub.