33k views and 80+ stars in 24 hours — thank you. Your feedback drove this:
What's New
Attention History Tracking Every turn now logs to `~/.claude/attention_history.jsonl`. Query your trajectory:
```bash python3 ~/.claude/scripts/history.py --since 2h python3 ~/.claude/scripts/history.py --file ppe --transitions [12:22:35] Instance A | Turn 26 Query: what divergence dynamics? HOT: divergent.md, t3-telos.md, cvmp-transformer.md WARM: pipeline.md, orin.md (+3 more) ⬆ Promoted to HOT: divergent.md
Fractal Documentation Nested paths now activate correctly. modules/t3-telos/trajectories/convergent.md triggers parent co-activation.
Update cd ~/.claude-cognitive && git pull cp scripts/history.py ~/.claude/scripts/
MirrorEthic•1mo ago
The problem: Claude Code is stateless. Every new instance rediscovers your architecture from scratch, hallucinates integrations that don't exist, repeats debugging you already tried, and burns tokens re-reading unchanged files.
At 1M+ lines of Python (3,400 modules across a distributed system), this was killing my productivity.
The solution is two systems:
1. Context Router – Attention-based file injection. Files get HOT/WARM/COLD scores based on recency and keyword activation. HOT files inject fully, WARM files inject headers only, COLD files evict. Files decay over turns, co-activate with related files. Result: 64-95% token reduction.
2. Pool Coordinator – Multi-instance state sharing. Running 8 concurrent Claude Code instances, they now share completions and blockers. No duplicate debugging, no stepping on each other.
Results after months of daily use: - New instances productive on first message - Zero hallucinated imports - Token usage down 70-80% average - Works across multi-day sessions
Open source (MIT). Works with Claude Code today via hooks.
GitHub: https://github.com/GMaN1911/claude-cognitive
Happy to answer questions about the architecture or implementation details.
mehmetkose•1mo ago
MirrorEthic•1mo ago
This is dynamic attention routing. Files get scored based on what you're actively discussing. mention "auth" and auth-related docs go HOT (full injection), related files go WARM (headers only), unrelated files stay COLD (evicted).
Scores decay over turns. If you stop talking about auth, those files fade back to COLD automatically.
Plus multi-instance coordination, concurrent Claude sessions sharing completions and blockers so they don't duplicate work.
25k character limit on injection, so you compact less and stay focused where its needed. Ive also seen it help alot with the post compacting context wobble that occurs.
mehmetkose•1mo ago
MirrorEthic•1mo ago
Token reduction: 64-95% depending on codebase size and work pattern. The variance is because it depends on how many files are in your .claude/ directory and how focused your session is.
How to measure yourself: 1. Check `~/.claude/attention_history.jsonl` after a session 2. Run `python3 ~/.claude/scripts/history.py --since 2h` to see what got injected vs evicted 3. Compare your token counts before/after in Claude Code's usage stats
The 25k character injection cap is the key constraint (adjustable), forces the router to prioritize ruthlessly instead of dumping everything in.
A proper benchmark comparing baseline Claude Code vs claude-cognitive on identical tasks would be useful. If someone wants to build that, I'd happily collaborate.
MirrorEthic•1mo ago