Show HN: Local-first semantic knowledge graph with magnetic-pull retrieval Rig launched a local-first semantic knowledge graph tool that transforms codebases into interactive, navigable maps for AI coding agents. The tool runs entirely on the user's machine with no API keys or data uploads, enabling agents to query code by structure, meaning, and historical context rather than relying on blind grep searches. Watch your codebase become a constellation — and give your AI agent a map of it. https://github.com/Astralchemist/rig/releases/download/v0.1.0/demo.mp4 ▶ Watch the full demo with audio https://github.com/Astralchemist/rig/releases/download/v0.1.0/demo.mp4 Rig builds a local-first semantic knowledge graph of your project, renders it as an interactive map you can fly through, and exposes it to coding agents Claude Code, Cursor, Codex, … over MCP. Your agent stops grepping blindly and starts navigating — by structure, by meaning, and by what it's touched before. Everything runs on your machine. No API key, no upload, nothing leaves your laptop. In any project directory: npx rig-constellation Have Bun https://bun.sh ? bunx rig-constellation works too. That's the whole thing. One command: ⬡ Rig — mapping my-project http://localhost:7491 ✓ initialized ./.rig ✓ map live http://localhost:7491 → 1/6 extract ██████████████████ 212/212 → 5/6 hubness ████████████████░░ ✓ indexed 1,204 nodes · 3,891 edges · 212 files · 36 skills ✓ wired claude press Ctrl-C to stop the map. It initializes .rig/ , opens the live map first , then indexes your code so the graph assembles in the already-open browser tab in real time, and wires up whichever agent it detects. The map title and port are derived per project, so two checkouts can run side by side on stable, distinct ports. Re-run any time, or use the explicit subcommands below. The command is rig alias: rig-constellation . Prefer a global install? npm i -g rig-constellation or bun install -g rig-constellation , then rig start . Installed locally with npm i rig-constellation ? The binary lives in node modules/.bin — run it with npx rig start or install with -g to get rig on your PATH . A map of your codebase. Files, symbols, calls, imports, and dependencies as a navigable graph — not a file tree. Magnetic pull. Ask "what's related to X" and get a ranked answer that blends graph distance, semantic similarity, and what's been active recently. Hubs. The structurally important anchors surface first, so a 5k-node graph stays legible. Dependency intelligence. "What version of X do I have?" and "what's declared but never imported?" become one-hop graph queries. Waypoints. Your agent drops durable markers at decisions and constraints that survive context-window compaction — so a new session picks up oriented. An MCP tool surface your agent calls directly: search, pull, callers/callees, impact, hubs, deps, and more. Without a map, an agent answers "what breaks if I change parseConfig?" by grepping the string and reading whatever files match — blind, lossy, and token-expensive. With Rig it's one call: rig impact parseConfig → 7 transitive callers, ranked: loadSettings calls · depth 1 bootstrap calls · depth 2 tests /config… tests · depth 1 … And "what else should I look at?" isn't a guess — rig pull returns related anchors scored by graph distance, on-device embedding similarity, and recent activity, with the three components broken out so the ranking is explainable, not a black box : rig pull parseConfig → { node: "validateSchema", score: 0.81, components: { structural: 0.4, semantic: 0.9, recency: 0.7 } } That ranked, self-explaining retrieval — not a flat grep dump — is the difference. - Embeddings run locally via a small on-device model bge-small . No API key required. - The graph lives in .rig/rig.db in your project. rig auto-adds .rig/ to your .gitignore . - Nothing is uploaded. The map UI is served on loopback only. bunx rig-constellation auto-detects and wires the agents you have installed. To wire one explicitly: rig install claude also: cursor · codex · opencode · openrouter This merges Rig's MCP server into the agent's config; the agent spawns rig serve --mcp on demand. | Command | What it does | |---|---| rig start | One-shot: init + index + wire agent + open the live map | rig index | Extract + write nodes --include / --exclude