feat(core,mcp): persistent relational code graph#1
Merged
Conversation
- .nvmrc 20 -> 22 so better-sqlite3 uses published macOS arm64 prebuilds - add .npmrc (ignore-scripts=false) so the native SQLite deps run install hooks - smoke-pack-install: force ignore-scripts=false for the packed-install check - README: document the Node 22 + .npmrc requirement Pre-existing local environment setup; committed alongside the graph work because the build/test gate depends on Node 22. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
…s/impl/impact)
Adds a persistent, incrementally-maintained `edges` graph so codesift can
answer relational queries grep structurally cannot — who calls/references X,
what imports a file, who implements an interface, and bounded impact
("what breaks if I change X") — all index-time, zero-egress, and honestly
labeled import-resolved vs name-only.
Phases (per GRAPH_PLAN.md):
- 0: edges table + indexes, per-file plumbing in applySyncChanges,
SCHEMA_VERSION 7->8, Edge/EdgeKind/EdgeResolution types.
- 1: index-time edge extraction for TS/JS + Python riding the cached
chunking AST; caller attribution by enclosing range; with_usages now
reads the index instead of re-parsing files at query time.
- 2: core findCallers/findReferences/findImporters + MCP tools
find_callers / find_refs / find_importers.
- 3: TS implements/extends heritage edges; name-only call edges for
Go/Java/Ruby/Rust; findImplementers + who_implements.
- 4: opt-in find_symbol relations bundle (with_callers) and bounded
impact(name, depth) BFS (hard node/depth caps + cycle guard) + impact tool.
Reviewed and fixed: default-export resolution, name-only leakage into
disambiguated queries, shadow/member-access mislabeling, case-insensitive
edge matching, and stale-inbound-edge cleanup on file removal.
Honesty: never type-resolved; name-only surfaced as approx. Additive — no
ranking/fusion/search behavior changed. Gate green on Node 22
(pnpm build && typecheck && test: 11 files, 177 tests).
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
rutvikchandla3
force-pushed
the
feat/relational-code-graph
branch
from
June 20, 2026 09:08
82fbe1d to
f2e679c
Compare
rutvikchandla3
force-pushed
the
feat/relational-code-graph
branch
from
June 20, 2026 09:11
f2e679c to
16cc515
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Notes