Persistent memory and pattern tracking for Claude Code sessions.
Claude Code learns from your failures and successes, building institutional knowledge that persists across sessions. Patterns strengthen automatically. Install once, watch knowledge compound over weeks.
./install.sh # Mac/Linux
./install.ps1 # WindowsEvery session, start with check in. This is the most important habit:
You: check in
Claude: [Queries building, starts dashboard, returns golden rules + heuristics]
What "check in" does:
- First time ever: Installs hooks, initializes database, starts dashboard
- Start of session: Loads knowledge, starts dashboard at http://localhost:3001 (Ctrl+click to open)
- When stuck: Searches for relevant patterns that might help
- Before closing: Ensures learnings are captured (CYA - cover your ass)
When to check in:
| Moment | Why |
|---|---|
| Start of every session | Load context, start dashboard, prevent repeating mistakes |
| When you hit a problem | See if building knows about this issue |
| Before closing session | Ensure learnings are captured |
| Feature | What It Does |
|---|---|
| Persistent Learning | Failures and successes recorded to SQLite, survive across sessions |
| Heuristics | Patterns gain confidence through validation (0.0 -> 1.0) |
| Golden Rules | High-confidence heuristics promoted to constitutional principles |
| Pheromone Trails | Files touched by tasks tracked for hotspot analysis |
| Coordinated Swarms | Multi-agent workflows with specialized personas |
| Local Dashboard | Visual monitoring at http://localhost:3001 (no API tokens used) |
Overview - Hotspot treemap showing file activity, anomalies, and golden rules at a glance
Heuristics - Browse and manage learned patterns with confidence scores
Knowledge Graph - Interactive visualization of heuristic relationships across domains
Analytics - Track learning velocity, success rates, and confidence trends over time
+---------------------------------------------------+
| The Learning Loop |
+---------------------------------------------------+
| QUERY -> Check building for knowledge |
| APPLY -> Use heuristics during task |
| RECORD -> Capture outcome (success/failure) |
| PERSIST -> Update confidence scores |
| | |
| (cycle repeats, patterns strengthen) |
+---------------------------------------------------+
| Say This | What Happens |
|---|---|
check in |
Start dashboard, query building, show golden rules + heuristics |
query the building |
Same as check in |
what does the building know about X |
Search for topic X |
record this failure: [lesson] |
Create failure log |
record this success: [pattern] |
Document what worked |
# Check what has been learned
python ~/.claude/emergent-learning/query/query.py --stats
# Start dashboard manually (if needed)
cd ~/.claude/emergent-learning/dashboard-app && ./run-dashboard.sh
# Multi-agent swarm (Pro/Max plans)
/swarm investigate the authentication system| Agent | Role |
|---|---|
| Researcher | Deep investigation, gather evidence |
| Architect | System design, big picture |
| Skeptic | Break things, find edge cases |
| Creative | Novel solutions, lateral thinking |
Full documentation in the Wiki:
- Installation - Prerequisites, options, troubleshooting
- Configuration - CLAUDE.md, settings.json, hooks
- Dashboard - Tabs, stats, themes
- Swarm - Multi-agent coordination, blackboard pattern
- CLI Reference - All query commands
- Golden Rules - How to customize principles
- Migration - Upgrading, team setup
- Architecture - Database schema, hooks system
- Token Costs - Usage breakdown, optimization
| Plan | Core + Dashboard | Swarm |
|---|---|---|
| Free | Yes | No |
| Pro ($20) | Yes | Yes |
| Max ($100+) | Yes | Yes |
MIT License
