zeroclaw-labs/zeroclaw · error

cli-alias-rename-reserved

cli-alias-rename-reserved

Error message

alias `{$alias}` is reserved and cannot be renamed

What it means

Error "alias `{$alias}` is reserved and cannot be renamed" thrown in zeroclaw-labs/zeroclaw.

Source

Thrown at src/alias_cli/mod.rs:331

            Ok(())
        }
        Err(RenameError::NotFound(p)) => bail!(
            "{}",
            mta(
                "cli-alias-not-configured",
                &[("path", p.as_str())],
                "{$path} is not configured"
            )
        ),
        Err(RenameError::InvalidName(m)) => bail!(
            "{}",
            mta(
                "cli-alias-rename-invalid",
                &[("message", m.as_str())],
                "invalid new alias: {$message}"
            )
        ),
        Err(RenameError::Reserved(a)) => bail!(
            "{}",
            mta(
                "cli-alias-rename-reserved",
                &[("alias", a.as_str())],
                "alias `{$alias}` is reserved and cannot be renamed"
            )
        ),
        Err(RenameError::PostCondition(m)) => bail!(
            "{}",
            mta(
                "cli-alias-rename-postcondition",
                &[("message", m.as_str())],
                "rename cascade post-condition failed: {$message}"
            )
        ),
    }
}

View on GitHub (pinned to 88bb9c8533)

Solutions

1. Do not rename reserved aliases such as `default`; create a new alias instead.
2. Rename a non-reserved alias, or duplicate the config under a new name and delete the old one if allowed.

When it happens

Trigger: Thrown at src/alias_cli/mod.rs:331 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/03657bd7d6859d5b. Report an issue: GitHub.