BObochoh·Jan 9, 2026Submission
Working memory for Claude Code – persistent context and multi-instance coord
1 points · Open discussionGMaN1911
claude-cognitive
Python2025–2026
GMaN1911 / claude-cognitive
claude-cognitive
Working memory for Claude Code - persistent context and multi-instance coordination
2Distinct people
4Mentions
0Explicit recommenders
452GitHub stars
What to know before exploring
What it is
Working memory for Claude Code - persistent context and multi-instance coordination
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by day4 dated mentions
Observed mentions: 2025-12-30 22:27:22 UTC to 2026-01-09 01:09:10 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Dec 30 | 2025-12-30 00:00:00 UTC | 2025-12-31 00:00:00 UTC | 2 | 1 | 1 |
| Dec 31 | 2025-12-31 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 1 | 2026-01-01 00:00:00 UTC | 2026-01-02 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2 | 2026-01-02 00:00:00 UTC | 2026-01-03 00:00:00 UTC | 0 | 0 | 0 |
| Jan 3 | 2026-01-03 00:00:00 UTC | 2026-01-04 00:00:00 UTC | 0 | 0 | 0 |
| Jan 4 | 2026-01-04 00:00:00 UTC | 2026-01-05 00:00:00 UTC | 0 | 0 | 0 |
| Jan 5 | 2026-01-05 00:00:00 UTC | 2026-01-06 00:00:00 UTC | 0 | 0 | 0 |
| Jan 6 | 2026-01-06 00:00:00 UTC | 2026-01-07 00:00:00 UTC | 0 | 0 | 0 |
| Jan 7 | 2026-01-07 00:00:00 UTC | 2026-01-08 00:00:00 UTC | 0 | 0 | 0 |
| Jan 8 | 2026-01-08 00:00:00 UTC | 2026-01-09 00:00:00 UTC | 0 | 0 | 0 |
| Jan 9 | 2026-01-09 00:00:00 UTC | 2026-01-10 00:00:00 UTC | 2 | 1 | 1 |
What Hacker News says
4 sourcesI’ve had decent results with this for context management in large code bases so far https://github.com/GMaN1911/claude-cognitive
In How to code Claude Code in 200 lines of codeShow HN: Claude Cognitive – Working memory for Claude Code
15 points · Open discussionI built Claude Cognitive because Claude Code kept forgetting my codebase between sessions.
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 com
Read the rest
pletions 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.