Who it is forA developer with many side projects who is about to write code that may already exist in an older repository.
The problemSearching for past work with grep, find and ls across many folders takes minutes and often points to the wrong repo.
The outcomeA ranked list of matching paths across all indexed projects, each with a verdict, so you can reuse the work or skip the rebuild.
What you need first
- Node.js with npm, to run `npm i -g @arihantdeva/heimdall`
- macOS or a Debian, Ubuntu, Fedora or Amazon Linux machine, with the build prerequisites listed in the README for the graft backend
- git, because llama.cpp is cloned at first build
- A supported agent harness: pi, Claude Code, Codex, Cursor, Windsurf, or opencode
Steps
npm i -g @arihantdeva/heimdallheimdall init --harness claude-codeheimdall setupheimdall doctorheimdall search "<topic>"(inferred, check the README)
Prompt for your agent
Using the heimdall CLI from the ArihantDeva/heimdall repo, run `heimdall search "<topic>"` before writing new code for <topic>. Report each hit as a line with its verdict (STRONG, WEAK, REBUILT, STALE or REMOVED) and its path. Expected output is a ranked list of paths; check that each STRONG path exists on disk before reusing it.
Caveat. The README says `npm i -g` builds the graft backend during install only when prerequisites are present, and the first build takes a few minutes, so search will not work until setup completes.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for ArihantDeva/heimdall and "Find a solution you already built in another repo"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer