Repository navigation
Replies: 3 comments
|
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. |
|
Thank you again for featuring the project and its contributors. Following up on this older thread: there is no action needed from you, and the community's reports and contributions remain a large part of the work behind the project. We appreciate the coverage. |
|
Thanks Martin, and thanks for circling back. That’s exactly the kind of story we like to tell. We’ll keep cheering on the codebase-memory-mcp community from the sidelines and keep an eye on what comes next. Keep shipping! 🚢🚢🚢 |
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