From atum-global-brain
Guide on how to use the atum-global-brain persistent memory, journaling, and context routing systems.
npx claudepluginhub arnwaldn/atum-plugins-collection --plugin atum-global-brainThis skill uses the workspace's default tool permissions.
`atum-global-brain` is a persistent, cross-session, and zero-dependency memory system for Claude Code / Claude Desktop. It provides 8 tools exposed via an MCP server to give Claude a "brain".
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Executes pre-written implementation plans: critically reviews, follows bite-sized steps exactly, runs verifications, tracks progress with checkpoints, uses git worktrees, stops on blockers.
Guides idea refinement into designs: explores context, asks questions one-by-one, proposes approaches, presents sections for approval, writes/review specs before coding.
atum-global-brain is a persistent, cross-session, and zero-dependency memory system for Claude Code / Claude Desktop. It provides 8 tools exposed via an MCP server to give Claude a "brain".
Memory entries are stored in ~/.claude/brain/memory/ as JSONL files.
There are three types of memories:
Use the brain_remember tool to store knowledge.
Always provide relevant tags (e.g., ["react", "auth"]) to make it easily searchable.
If you are asked to remember something explicitly by the user, you can set the source to user-explicit and confidence to 0.9.
Use the brain_recall tool to fetch prior knowledge. It uses a lightweight TF-IDF search combined with tag matching. Use it whenever you face a recurring issue to see if a lesson was learned previously.
Use the brain_journal tool to write notes in the daily journal (~/.claude/brain/journal/YYYY-MM-DD.md).
This acts as your persistent scratchpad. Categories include:
plan: Write an implementation plan here BEFORE modifying multiple files.doubt: Write any uncertainty here to prompt user clarification.hypothesis: Write what you think the bug is BEFORE testing.reflection: General introspection.todo: Track pending tasks.Use brain_reflect to summarize activity over the today, week, or month scope.
If you are unsure which plugins or skills are relevant to a user query, call brain_suggest_context(user_query="...") and the brain will recommend the primary plugin and supporting skills, along with pulling relevant memories.
The brain comes with optional hooks:
brain-session-start.js: Injects project context at the beginning of a session.brain-session-end.js: Triggers project status updates and session reflection at the end.