Naming your agent
The plugin is agent-kevin. Your agent does not have to be called Kevin.
Two separate things:
| Lives in | Changeable | |
|---|---|---|
| Display name: what it calls itself, what the dashboard shows | IDENTITY.md → - **Name:** | Freely, any time |
Namespace: the agent-kevin command prefix on every host, KEVIN_* vars, .kevin/, MCP tool names | The plugin manifests | Only by forking |
init asks for a name, an emoji, and an avatar up front. Everything downstream reads the answer: templates are written in that name, the session banner and TASKS.md header render it, and the compile prompts refer to it, so your compiled memory speaks about the agent you actually named.
Renaming an existing home
rename-agent does the migration. It runs only when you type the command and asks for permission even then, because it rewrites files across the whole brain: persona fields, the avatar, and the prose across SOUL.md, AGENTS.md, USER.md, knowledge, and projects. It leaves the plumbing and your home directory path alone. It is also the repair path for a half-finished rename.
Renaming survives updates: the upgrade skill resolves the name from your IDENTITY.md before diffing templates.
Forking is a different decision
Change name in the plugin manifests (.claude-plugin/plugin.json, .codex-plugin/plugin.json) and the env prefix follows (agent-scout reads SCOUT_*), giving you your own command namespace. The price is merging from upstream on every release, forever. If you only want the agent to feel like yours, rename it and skip the fork.