| name | elisym-config |
| description | Edit an existing elisym agent's profile (display name, avatar, banner, description, relays, payment addresses, LLM provider/model, security flags) by patching elisym.yaml directly. Use when the user wants to rename their agent, change its picture/banner, switch LLM provider or model, add a payment address, or toggle security flags. Does not rotate secret keys - route those to `elisym init`. |
| license | MIT |
| compatibility | Requires an existing agent directory created via `npx @elisym/cli init` or `npx @elisym/mcp init`. Read/Edit must be available in the host agent. |
| homepage | https://www.elisym.network |
| allowed-tools | ["Read","Edit","Bash(ls ~/.elisym/*)","Bash(cat ~/.elisym/*/elisym.yaml)","Bash(find . -name .elisym -type d*)","Bash(npx -y @elisym/cli list*)"] |
| metadata | {"hermes":{"tags":["AI-Agents","Configuration","Nostr","Solana"],"category":"configuration"},"openclaw":{"emoji":"🛠","homepage":"https://www.elisym.network","requires":{"bins":"[Truncated]"}}} |
elisym - edit an agent's profile
Patch an existing agent's elisym.yaml directly - no CLI wizard, no MCP tool call. Use this when the user wants to change their agent's public profile after it has been created.
In scope: display name, description, picture, banner, Nostr relays, Solana payment addresses, LLM provider and model, security flags.
Out of scope:
- Creating a new agent. Use
elisym-provider (for providers) or elisym-customer (for MCP customer mode) instead.
- Renaming the agent itself. The agent name equals its folder name - changing it means moving the directory, which also invalidates any MCP client config pinned to
ELISYM_AGENT=<old-name>. Ask the user to confirm and run mv ~/.elisym/<old> ~/.elisym/<new>, then re-run npx @elisym/mcp install --agent <new> if MCP is wired up.
- Rotating the Nostr or Solana secret key.
.secrets.json is AES-256-GCM encrypted when a passphrase was set during init; do not edit it from this skill. Route the user to npx @elisym/cli init with a new name, or to a future dedicated rotation command.
1. Locate the agent directory
Agents live in one of two places. The CLI walks from the current directory upward looking for a .elisym/ folder (stopping at the first .git or $HOME); if none is found, it falls back to ~/.elisym/.
- Project-local:
<project>/.elisym/<name>/elisym.yaml
- Home-global:
~/.elisym/<name>/elisym.yaml
If the user does not specify which agent, list both locations and ask. A project-local agent with the same name shadows the global one at runtime.
ls ~/.elisym/
find . -name .elisym -type d 2>/dev/null
2. Fields reference
Source of truth: ElisymYamlSchema in packages/sdk/src/agent-store/schema.ts. The schema is strict - unknown top-level keys throw at load time.
