Brains
A brain is a named snapshot of soul + persona + rules. Instead of switching three things separately, save your setup once and activate it in one command.
Saving a brain
Section titled “Saving a brain”Set up the configuration you want, then snapshot it:
brainjar soul use craftsmanbrainjar persona use reviewerbrainjar rules add boundariesbrainjar rules add securitybrainjar brain save reviewActivating a brain
Section titled “Activating a brain”brainjar brain use reviewThis activates the soul, persona, and all rules from the snapshot in one shot.
Managing brains
Section titled “Managing brains”brainjar brain list # See available brainsbrainjar brain show review # Inspect a brain's configbrainjar brain drop review # Deactivate a brain (clears soul, persona, rules)brainjar brain delete review # Permanently delete a brainBrain vs. individual layers
Section titled “Brain vs. individual layers”| Approach | When to use |
|---|---|
| Brain | Repeatable workflow you do often (code review, design, debugging) |
| Individual layers | Exploratory work, one-off overrides, or changing one thing |
Brains and compose
Section titled “Brains and compose”Brains are the primary input to compose, which assembles a full prompt for subagent dispatch:
mcp__brainjar__compose(brain="review", task="Review the changes in src/sync.ts")This returns the complete prompt (soul + persona + rules + task) ready to pass to Claude Code’s Agent tool. See Subagent Orchestration for compose basics and Orchestration Patterns for multi-agent workflow patterns.