Plugins & Personas

Personas

A persona is not just a system prompt. It's a system prompt plus a dedicated mind and memory system that grows organically as you use it.

When a persona is active, every fact the agent learns, every decision it makes, and every pattern it recognizes gets stored under that persona's identity. In future sessions with the same persona, those facts are recalled — the persona remembers what it learned. This is the difference between a prompt template and a living cognitive profile.

Usage

# Activate a persona
/persona architect

# Deactivate
/persona off

# The agent shows the active route and persona in metadata:
# provider:model · provider · grade B · ⌘ architect

What Personas Control

• System prompt — base instructions and cognitive style
• Memory namespace — facts stored under the persona's identity
• Badge — visual identifier in the TUI and meta tags
• Preferred tools — which tools the persona tends to reach for

Tones

Tones adjust the agent's communication style without changing its capabilities or memory. They're lighter than personas — no dedicated memory, just a style overlay.

/tone concise    # Terse, minimal explanations
/tone teaching   # Explains reasoning, suggests learning paths
/tone off        # Default communication style

Plugin Registry

The plugin registry manages active persona, tone, and memory layers. It's responsible for:

• Loading and validating persona definitions
• Merging persona system prompts with the base Lex Imperialis (core system prompt)
• Routing memory operations to the correct namespace
• Showing persona/tone state changes as toast notifications

Dynamic tool inventory

Tool visibility is assembled at runtime from core tools, enabled capability groups, extensions, project configuration, persona policy, and the current provider surface. The running inventory—not a fixed documentation list—is authoritative.

• Use manage_tools to list, enable, or disable situational capability groups.
• Use /profile and /settings to inspect operator-selected runtime defaults.
• Project and persona policy can narrow tool availability; enabling a group does not bypass permissions.