CLclemens1010·Aug 17, 2026
We rely on a tree-sitter based tool https://github.com/DeusData/codebase-memory-mcp
In Show HN: Code review that follows callers across your reposDeusData
codebase-memory-mcp
C2026–2026
DeusData / codebase-memory-mcp
codebase-memory-mcp
Local code intelligence for developers and AI agents. Connect code, docs and infrastructure in a persistent graph, with CBM Lens, MCP tools, agent integrations and change-aware test selection.
Developer ToolsCommand LineData & DatabasesSystems & InfrastructureAI & Machine LearningLearning & ReferenceTesting & Quality
8Distinct people
9Mentions
0Explicit recommenders
48.6KGitHub stars
What to know before exploring
What it is
Local code intelligence for developers and AI agents. Connect code, docs and infrastructure in a persistent graph, with CBM Lens, MCP tools, agent integrations and change-aware test selection.
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, 11:56:56 AM 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 week9 dated mentions
Observed mentions: 2026-03-03 16:08:10 UTC to 2026-08-17 13:10:35 UTC. Weeks start Monday, 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 |
|---|---|---|---|---|---|
| Mar 2 | 2026-03-02 00:00:00 UTC | 2026-03-09 00:00:00 UTC | 1 | 1 | 0 |
| Mar 9 | 2026-03-09 00:00:00 UTC | 2026-03-16 00:00:00 UTC | 0 | 0 | 0 |
| Mar 16 | 2026-03-16 00:00:00 UTC | 2026-03-23 00:00:00 UTC | 0 | 0 | 0 |
| Mar 23 | 2026-03-23 00:00:00 UTC | 2026-03-30 00:00:00 UTC | 0 | 0 | 0 |
| Mar 30 | 2026-03-30 00:00:00 UTC | 2026-04-06 00:00:00 UTC | 0 | 0 | 0 |
| Apr 6 | 2026-04-06 00:00:00 UTC | 2026-04-13 00:00:00 UTC | 1 | 1 | 0 |
| Apr 13 | 2026-04-13 00:00:00 UTC | 2026-04-20 00:00:00 UTC | 0 | 0 | 0 |
| Apr 20 | 2026-04-20 00:00:00 UTC | 2026-04-27 00:00:00 UTC | 0 | 0 | 0 |
| Apr 27 | 2026-04-27 00:00:00 UTC | 2026-05-04 00:00:00 UTC | 0 | 0 | 0 |
| May 4 | 2026-05-04 00:00:00 UTC | 2026-05-11 00:00:00 UTC | 0 | 0 | 0 |
| May 11 | 2026-05-11 00:00:00 UTC | 2026-05-18 00:00:00 UTC | 1 | 0 | 1 |
| May 18 | 2026-05-18 00:00:00 UTC | 2026-05-25 00:00:00 UTC | 0 | 0 | 0 |
| May 25 | 2026-05-25 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 0 | 0 | 0 |
| Jun 1 | 2026-06-01 00:00:00 UTC | 2026-06-08 00:00:00 UTC | 0 | 0 | 0 |
| Jun 8 | 2026-06-08 00:00:00 UTC | 2026-06-15 00:00:00 UTC | 0 | 0 | 0 |
| Jun 15 | 2026-06-15 00:00:00 UTC | 2026-06-22 00:00:00 UTC | 2 | 2 | 0 |
| Jun 22 | 2026-06-22 00:00:00 UTC | 2026-06-29 00:00:00 UTC | 0 | 0 | 0 |
| Jun 29 | 2026-06-29 00:00:00 UTC | 2026-07-06 00:00:00 UTC | 1 | 0 | 1 |
| Jul 6 | 2026-07-06 00:00:00 UTC | 2026-07-13 00:00:00 UTC | 0 | 0 | 0 |
| Jul 13 | 2026-07-13 00:00:00 UTC | 2026-07-20 00:00:00 UTC | 0 | 0 | 0 |
| Jul 20 | 2026-07-20 00:00:00 UTC | 2026-07-27 00:00:00 UTC | 0 | 0 | 0 |
| Jul 27 | 2026-07-27 00:00:00 UTC | 2026-08-03 00:00:00 UTC | 0 | 0 | 0 |
| Aug 3 | 2026-08-03 00:00:00 UTC | 2026-08-10 00:00:00 UTC | 1 | 0 | 1 |
| Aug 10 | 2026-08-10 00:00:00 UTC | 2026-08-17 00:00:00 UTC | 1 | 0 | 1 |
| Aug 17 | 2026-08-17 00:00:00 UTC | 2026-08-24 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
9 sourcesI think this adds no value. I would stick to OpenCode.
Things I would value: high-fidelity visualization (bonus points for Figma-like visual edits), good tool use (don't force me to tell the model), token efficiency, resource efficiency. Things that are not problems:
* Routing: OpenCode predefines subagents that you can set to appropriate models.
* Search: there are AST and embedding-based search MCPs. I use https://github.com/DeusData/codebase-memory-mcp
In Launch HN: Bullet (YC S26) – A Faster Coding AgentJust working on my own stuff so YMMV, but from a cost reduction standpoint, the two most outsized ROI wins came from making sure the agent runs all terminal commands in quiet and using a codebase index mcp to speed up understanding and reduce full file reads [0]. I've also found the latter also dramatically improved the quality of output.
[0] https://github.com/DeusData/codebase-memory-mcp
In Harness engineering for self-improvementI don't use local models but have you tried augmenting the model with code intelligence MCPs like https://github.com/DeusData/codebase-memory-mcp ?
In Qwen 3.6 27B is the sweet spot for local developmentHigh-performance code intelligence MCP server
3 points · Open discussionWould this replace something like codebase-memory-mcp[1] or improve when both is being used?
[1] - https://github.com/DeusData/codebase-memory-mcp
In Show HN: Semble – Code search for agents that uses 98% fewer tokens than grepAsk HN: SoTA of Context Building Methods
Hi HN, I am a very minimal AI user (I use stock vscode chat with no MCPs to ideate on plans), but recently I've been coming across context building MCPs/tools that build a knowledge graph of your codebase.
This is really interesting because I am working on pretty large codebases simultaneously and the idea that my agent won't have to re-index and re-read all my files over and over again is pretty enticing.
My question is what methods are you using to index and connect these to your agents?
My research has led me to the following but I am basically very confused by what metric to measure how good they are.
1. https://github.com/abhigyanpatwari/GitNexus - seems like the most popular
2. https://github.com/DeusData/codebase-memory-mcp - also interesting/new
3. https://github.com/JaredStewart/coderlm - the tree-sitter based approach seems real
Read the rest
ly good.
Would love to know how people actively using frontier models and methods navigate this domain.
I replaced grep-based code exploration with a knowledge graph – 10x less token
4 points · Open discussion