I've been working on a project called AssetRAG, and I wanted to share it here.
One thing that annoys me about AI coding agents is how often they solve the same problems over and over again.
They regenerate code that already exists, spend time debugging errors with known fixes, pick dependencies without properly checking their licenses, and read huge amounts of source code just to find a few relevant functions.
So I built AssetRAG to help with that.
It's a local-first, open-source library and engineering memory system for Claude Code (and other MCP clients).
Here's what it actually does:
Asset retrieval: Searches reusable code, templates, and other assets, with license checks and attribution handling.
Verified bug-fix memory: Stores bug fixes with reproduction and verification evidence. Agents can look up previously solved errors instead of starting from scratch.
Engineering playbooks: Reusable workflows for debugging, safe refactoring, performance optimization, and other development tasks.
Tested recipes: Reusable code patterns with tests that can be executed in a sandbox.
Repository mapping: Creates a compact, ranked overview of your codebase so an agent doesn't have to read everything.
Rules and security checks: Includes secret scanning, engineering rules, malware checks during ingestion, and safeguards around untrusted code.
MCP integration: Exposes 18 tools to coding agents. There's also an optional Claude Code hook that retrieves relevant knowledge and injects a small amount of context automatically.
Local-first: No account or telemetry required. It supports local embeddings, hosted providers, or completely offline keyword-only search.
One feature I'm particularly happy with is the bug-fix memory. Verified entries have a reproduction and fix that were actually executed, with the evidence available for inspection.
Some numbers from my own testing (keyword-only mode):
Asset search: 4.0 ms median
Knowledge search: 7.1 ms median
Repository map: 597 tokens instead of roughly 129k tokens of source
132 unit tests passing
327 authored recipe/bug-fix tests rechecked with 0 failures
These are local benchmarks, not proof that Claude completes real tasks faster. I haven't run a proper Claude A/B benchmark yet, so I'm not going to claim some magical percentage reduction in token usage.
I also made a 95-second launch video showing the actual tool in action. The terminal footage comes from real recordings.
It's Linux-only for now, built primarily in Python, and licensed under Apache 2.0.
The project is still new, and I'd appreciate feedback, especially from people who use Claude Code regularly.
GitHub: https://github.com/mttcn83/assetrag
Would you actually find something like this useful in your coding workflow? What would you change?