/emerge does a deep scan of your vault to find ideas you’ve been circling without ever naming. It looks for the conclusion hiding in your scattered premises, the pattern you keep writing about without formalizing, and the direction your actions are pointing without a conscious decision.
Usage
Type/emerge in Claude Code to start a vault-wide emergence scan.
What it looks for
/emerge works by reading across your vault and finding three types of implied thinking:
Scattered premises
Scattered premises
Ideas you’ve mentioned in different contexts — across daily notes, research, and reflections — that together form a larger conclusion you haven’t yet written down explicitly.
Unnamed patterns
Unnamed patterns
Recurring themes that appear across your writing but haven’t been named, tagged, or formalized into a standalone note or framework.
Unarticulated directions
Unarticulated directions
Where your actual behavior, interests, and decisions are pointing — even if you haven’t consciously chosen that direction yet.
Where it reads
/emerge scans the following vault zones:
| Zone | What it’s looking for |
|---|---|
thinking/ | Developed ideas and patterns |
daily/ | What you’ve actually been thinking about day to day |
personal/research/ | Topics you’ve been investigating |
context/ | Your stated values, goals, and self-understanding |
How an emergence session works
Run the scan
Type
/emerge. Claude reads across all four vault zones looking for implied conclusions, unnamed patterns, and unarticulated directions.Review the findings
Claude presents its findings as emergent insights — ideas that your vault implies but you haven’t explicitly stated.