Commands Reference
Entity Management
/create
Create a new entity.
/create [name]Examples:
/create Aria # Create entity named Aria
/create # Opens modal for name and facts/view
View an entity and its facts or memories.
/view <entity> [type]The optional type parameter controls what is shown:
| Value | Shows |
|---|---|
All (facts + memories) | Facts and memories (default) |
Facts only | Facts only |
Memories only | Memories only |
Examples:
/view Aria # View facts and memories
/help # View top-level help (help entities are hidden from /view)
/help expressions # View a help subtopic/edit
Edit an entity's facts, memories, config, or template.
/edit <entity> [type]The optional type parameter selects what to edit:
| Value | Opens |
|---|---|
Both | Facts and memories combined (default) |
Facts only | Facts only (more space, up to 4 fields) |
Memories only | Memories only |
Template | Nunjucks template (system prompt formatting) |
System Prompt | Per-entity system instructions |
Config | Model, context, stream, avatar, memory settings |
Advanced | Thinking level |
Permissions | View, edit, use, and blacklist permissions |
Examples:
/edit Aria # Edit facts and memories
/edit Aria type:Facts only # Edit only facts
/edit Aria type:Config # Edit model and settings
/edit Aria type:Permissions # Edit permissions
/edit Aria type:Template # Edit Nunjucks template
/edit Aria type:System Prompt # Edit system instructions/delete
Delete an entity you own.
/delete <entity>Only the owner can delete an entity.
Examples:
/delete Aria # Delete Aria/transfer
Transfer entity ownership to another user.
/transfer <entity> <user>Only the current owner can transfer an entity.
Examples:
/transfer Aria @username # Transfer Aria to another userBindings
/bind
Bind a Discord channel, server, or yourself to an entity.
/bind <target> <entity>Targets:
This channel- Entity responds in this channelThis server- Entity responds in all channels of this serverMe (this channel)- Speak as entity in this channel onlyMe (this server)- Speak as entity server-wideMe (global)- Speak as entity everywhere
Examples:
/bind "This channel" Aria # Aria responds here
/bind "This server" Narrator # Narrator responds server-wide
/bind "Me (this channel)" Traveler # Speak as Traveler here
/bind "Me (this server)" Knight # Speak as Knight server-wide/unbind
Remove an entity binding from a channel, server, or yourself.
/unbind <target> <entity>Targets:
This channel- Unbind from this channelThis server- Unbind from this serverMe (this channel)- Remove channel-specific personaMe (this server)- Remove server-wide personaMe (global)- Remove global persona
Examples:
/unbind "This channel" Aria # Remove Aria from this channel
/unbind "Me (this channel)" Traveler # Stop speaking as Traveler here
/unbind "Me (this server)" Knight # Remove server-wide personaServer Configuration
/config
Configure bind and persona permissions for a channel or server. Requires Manage Channels.
/config <scope>Scopes:
This channel- Configure permissions for the current channelThis server- Configure permissions server-wide
Opens a modal with three permission lists:
| Field | Controls |
|---|---|
| Bind access | Who can bind entities here (blank = everyone) |
| Persona access | Who can use personas here (blank = everyone) |
| Blacklist | Blocked from all binding operations |
Each field accepts users and roles. Clearing all fields removes the configuration (everyone can bind).
/config-chain
Set or clear the response chain limit for a channel or server. Requires Manage Webhooks.
/config-chain <scope>Scopes:
This channel- Override for the current channelThis server- Override server-wide
Opens a modal with a single field: enter a number from 0–20 to cap the self-response chain, or leave blank to inherit the server/global default (MAX_RESPONSE_CHAIN env var, default 3). Use 0 to prevent entities from responding to each other's messages entirely — they will only respond to human messages.
The channel-level override takes precedence over the server-level override, which takes precedence over the environment variable.
Moderation
/admin
Moderation tools: mutes, kill switches, rate and chain config, and audit log. Visible to users with Manage Messages at minimum. Each subcommand enforces its own permission requirement.
/admin mute create
/admin mute create target:<name-or-id> scope:<entity|owner|channel|server|global> duration:<10m|1h|1d|forever> [reason:<text>]Mute an entity or owner. Permissions vary by scope:
entityorownerscope at channel level: Manage Messagesserverorglobalscope: Manage Webhooks (global also requires Administrator)
After muting, the affected entity/owner no longer responds until the mute expires or is removed.
/admin mute list
/admin mute list [scope:<entity|owner|channel|server>] [target:<name-or-id>]List active mutes, optionally filtered. Shows mute IDs for use with /admin mute remove. Requires Manage Messages.
/admin mute remove
/admin mute remove id:<mute-id>Remove a mute by its ID (from /admin mute list). Requires Manage Messages.
/admin mute clear
/admin mute clear target:<name-or-id> [scope:<entity|owner>]Remove the most recently created mute for a target. Requires Manage Messages.
/admin disable channel / /admin enable channel
/admin disable channel [reason:<text>]
/admin enable channelKill switch for the current channel. No entity responds here until re-enabled. Requires Manage Channels.
/admin disable server / /admin enable server
/admin disable server [reason:<text>]
/admin enable serverGuild-wide kill switch. No entity responds in any channel of this server until re-enabled. Requires Manage Webhooks.
/admin config rate
/admin config rate scope:<channel|server>Opens a modal to set per-channel and per-owner response rate limits (messages per minute). Leave a field blank to remove its limit. Requires Manage Webhooks.
/admin config chain
/admin config chain scope:<channel|server>Opens a modal to set the max consecutive entity-to-entity response chain depth. Same behavior as /config-chain. Requires Manage Webhooks.
/admin audit
/admin audit [filter:<rate_limits|mutes|config_changes|all>] [target:<name-or-id>] [hours:<N>]View recent moderation events (rate limit hits, mutes, config changes). Defaults to the last 24 hours. Requires Manage Messages.
Status and Debugging
/debug
View current channel state or debug information.
/debug [subcommand]| Subcommand | Description |
|---|---|
status (default) | Channel bindings, your persona, unread message count |
prompt [entity] | System prompt that would be sent to the LLM |
context [entity] | Message context that would be sent to the LLM |
rag [entity] [query] | Embedding status and RAG retrieval test results |
For prompt, context, and rag, entity defaults to the channel-bound entity.
Examples:
/debug # Channel state
/debug status # Same as above
/debug prompt # System prompt for bound entity
/debug prompt Aria # System prompt for Aria
/debug context Aria # Message context for Aria
/debug rag Aria "silver" # Test RAG retrieval with queryTrigger
/trigger
Manually trigger an entity to respond in the current channel. Bypasses the normal response logic ($respond / $if) — the entity will always respond.
/trigger <entity> [verb]Respects $use and $blacklist permissions — you must be allowed to trigger the entity.
With a verb (entity-to-entity interaction):
The optional verb parameter sets interaction_type in the triggered entity's context, letting it react based on how it was interacted with. Requires you to have a persona bound (via /bind) — the interaction is attributed to your character, not to you directly.
/trigger HealthPotion drink # Your persona drinks the potion
/trigger StoneDoor open # Your persona opens the doorThe triggered entity can then use $if interaction_type == "drink" to only respond to that specific interaction.
Examples:
/trigger Aria # Force Aria to respond now
/trigger HealthPotion drink # Trigger HealthPotion with interaction_type "drink" (requires persona)History
/forget
Exclude all messages before this moment from the LLM context. Useful for resetting the "memory" of a conversation without deleting any messages.
/forgetMessages are not deleted — they remain in the database. They are simply excluded from the context window going forward.
Help
Help is an entity! Use /help:
/help # Overview
/help start # Getting started guide
/help commands # Command reference
/help expressions # Response control ($if)
/help patterns # Common expression patterns
/help facts # Fact patterns
/help bindings # Binding system
/help permissions # Entity permissions
/help models # LLM configurationAll help entities (help, help:start, help:commands, etc.) have owner-only $view, so they don't appear in /view autocomplete. The only public route is /help [topic], which bypasses view-perm checks.