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 active persona in the meta tag:
# claude-sonnet-4-6 · anthropic · victory · ⌘ 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

Tool Profiles

Tool profiles control which tools are visible in the agent's context. They reduce prompt bloat by only exposing relevant tools based on project type:

• core — always active: read, edit, write, bash, view
• coding — activated when .git detected: git tools, test runners
• visual — activated for .excalidraw / .d2 files
• local-ai — activated when Ollama is available
• web — always active: search tools

The agent can manage its own profiles with manage_tools, or operators can override with /profile.