Replies: 1 comment
|
Thank you — genuinely kind of you, and thanks for taking the time to come here and say so rather than just publishing. Glad the local-and-zero-telemetry angle is what stood out. That part is a deliberate constraint rather than a marketing line — it costs real diagnostic ability, since when someone hits a slow memory climb or a regression we have no data at all unless they choose to send it. Nice to see it read as a feature rather than an omission. Credit belongs to the contributors as much as anywhere; a lot of the language coverage and the platform-specific hardening came in through community PRs and bug reports from people running it on setups I could never test locally. Thanks again for the mention and the badge. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi all - we've featured codebase-memory-mcp in Repository Radar PR#38, our bi-weekly scan of open-source AI infrastructure, out tomorrow. A local, zero-telemetry knowledge graph over 158 languages in a single binary is exactly the kind of tool this issue is about. Congrats to Martin and the contributors 🙌 codebase-memory-mcp has earned a badge on repositoryradar.dev, and the full issue lands tomorrow at repositoryradar.substack.com.
All reactions