# Changelog

All notable changes to CodeGraph are documented here. Each entry also ships as
a [GitHub Release](https://github.com/colbymchenry/codegraph/releases) tagged
`vX.Y.Z`, which is where most people will look.

This project follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/)
and adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

## [Unreleased]


## [0.9.7] - 2026-05-28

### Added
- **Generated-file down-ranking across search, trace, and explore.** A new
  filename-based classifier (`src/extraction/generated-detection.ts`) flags
  protobuf / gRPC / mockgen / build-output files (`.pb.go`, `.pulsar.go`,
  `_grpc.pb.go`, `_mock.go`, `_mocks.go`, `mock_*.go`, `.generated.[jt]sx`,
  `_pb2(_grpc)?.py`, `.pb.{cc,h}`, `.g.dart`, `.freezed.dart`) and pushes them
  LAST in disambiguation. Before this, a `codegraph_search "Send"` on
  cosmos-sdk returned the gRPC interface stub at `tx_grpc.pb.go:124` as the
  first match — the trace landed on that empty stub, reported "no path", and
  the agent fell back to Read. With the down-rank applied to `findSymbol`,
  `findAllSymbols`, `codegraph_search`, the CLI `query` command, AND the
  context Entry Points / Related Symbols / Code blocks, the bank keeper's
  `msgServer.Send` (the real implementation) ranks #3 instead of #9 and
  trace lands on it directly. Pure path-based classifier — no schema change,
  no index migration.
- **gRPC interface→implementation bridge for Go.** New synthesizer
  `goGrpcStubImplEdges` in `src/resolution/callback-synthesizer.ts` finds
  `UnimplementedXxxServer` structs in `.pb.go` / `_grpc.pb.go` files,
  identifies their RPC-method signatures (excluding the `mustEmbed*` /
  `testEmbeddedByValue` gRPC markers), and links each stub method to the
  hand-written impl method on any struct whose method-name set is a
  superset. Closes Go's structural-typing gap that the Java/Kotlin-only
  `interfaceOverrideEdges` couldn't bridge. Excludes other generated files
  from candidate impls so a sibling `msgClient` in the same `.pb.go` doesn't
  get falsely paired. Measured on cosmos-sdk: 467 stub→impl `calls` edges
  synthesized, bank's `UnimplementedMsgServer::Send` now points only to
  `x/bank/keeper/msg_server.go::msgServer::Send` — not to mocks, not to
  client wrappers.
- **Trace-failure response now inlines both endpoints' bodies + neighbors.**
  When `codegraph_trace` can't find a static call path (typically a
  dynamic-dispatch break), it used to return a one-liner telling the agent
  to call `codegraph_node` next — which triggered 3-4 follow-up calls plus a
  Read. The new failure response inlines each endpoint's source (capped at
  120 lines / 3600 chars), callers, and callees in one response. On the
  cosmos-Q3 / etcd-Q2 audits this eliminated the entire fan-out pattern
  (5-11 codegraph calls collapsed into 1-2).
- **Path-proximity pairing in trace endpoint selection.** In a multi-module
  Go repo, a symbol like `EndBlocker` exists in 20+ modules; FTS picks one
  almost arbitrarily. Trace now scores every `from` × `to` candidate pair by
  shared directory prefix length (longest match wins) so
  `x/gov/abci.go::EndBlocker` + `x/gov/keeper/tally.go::Tally` are paired
  before `simapp/app.go`'s wrapper EndBlocker is even considered. A
  less-canonical-path penalty (`enterprise/`, `contrib/`, `examples/`,
  `vendor/`, `third_party/`, `deprecated/`, `legacy/`) ensures a side-module
  with a longer shared prefix doesn't beat the canonical module with a
  shorter one. FindPath probe budget capped at 20 pairs.
- **Test-file deprioritization in `codegraph_explore`.** Existing
  `isLowValue` only caught directory-style patterns (`/tests/`, `/spec/`);
  now also catches Go's `_test.go`, Ruby's `_spec.rb`, JS/TS `.test.ts` /
  `.spec.tsx`, and Java/Kotlin/Scala `*Test.java` / `*Spec.kt`. Without
  this, etcd's `watchable_store_test.go` consumed 5K chars of explore
  budget that should have gone to the hand-written flow source.
- **Small-repo retrieval tuning (`<500` indexed files).** Three coordinated
  changes so small projects resolve flow questions in 1-2 MCP calls instead
  of 3-5. (i) MCP tool surface drops to the 5 core tools
  (`codegraph_search` / `codegraph_context` / `codegraph_node` /
  `codegraph_explore` / `codegraph_trace`); the other 5 (`codegraph_callers`
  /`codegraph_callees`/`codegraph_impact`/`codegraph_status`/`codegraph_files`)
  cost more in tool-list overhead than they recoup at this scale.
  Empirically validated as the floor — n=2 audits showed cutting below
  5 regresses cobra/ky/sinatra (3-tool gate) and catastrophically regresses
  express (1-tool gate, +107% LOSS). (ii) `codegraph_context` responses end
  with a strong directive telling the agent the response IS the
  comprehensive pass for a project this size and follow-ups should be
  narrow (`trace from→to`, single-symbol `node`) — not another broad
  `codegraph_explore` that re-bundles the same content. (iii) Explore
  output budget gets a sub-150 tier (13K total / 4 files / 3.8K each,
  Relationships section dropped, test/spec/icon/i18n files hard-excluded
  from the relevant-file set unless the query is about tests), and
  `codegraph_context` `maxNodes` defaults to 8 instead of 20.
- **`codegraph_context` auto-traces flow queries.** When the task reads
  like "how does X reach Y", "trace the path from A to B", or "how does
  X propagate through Z", `codegraph_context` now runs the trace
  internally and splices its body into the response. Detection is
  conservative — needs a flow keyword AND ≥2 distinct PascalCase /
  camelCase identifiers, with the first two ordered by appearance taken
  as `from`/`to`. On dynamic-dispatch breaks it falls back to the
  trace-failure response (which already inlines both endpoint bodies +
  neighbors). Saves the follow-up `codegraph_trace` that was the #2
  cost driver on multi-module flow questions in the audit.
- **Routing-manifest inline in `codegraph_context` for small-repo
  routing queries.** When the task mentions
  routes/handlers/endpoints/middleware/etc. on a sub-500-file project,
  `codegraph_context` now appends a compact URL → handler table built
  from `route` nodes + their `references`/`calls` edges, then inlines
  the full source (≤16KB) of the file holding the most handler
  endpoints. Targets the Glob+Read pattern that was beating codegraph
  on realworld template repos (rails-realworld, laravel-realworld,
  drupal-admintoolbar, …) where the agent would just read `routes.rb` /
  `web.php` instead of asking the graph. Manifest is silently skipped
  when fewer than 3 non-test routes exist or no file holds ≥30% of
  them (no single answer file).
- **Core-directory ranking boost in `codegraph_context` search.**
  Projects with one file holding the dense majority of internal call
  edges (e.g. sinatra's `lib/sinatra/base.rb` at ~85% of all in-file
  edges) now get search results in that file's directory boosted by
  +25 score. Fixes the case where a small extension file with a
  verbatim name match outranks the actual framework core
  (sinatra-contrib's `multi_route.rb` `route` was outranking
  base.rb's `route!`). Test and generated files are excluded from
  "dominant file" candidacy so etcd's `rpc.pb.go` (1916 in-file
  edges, generated protobuf) can't beat the hand-written
  `server/etcdserver/server.go` (470 edges).
- **Interface → implementation synthesis extended beyond JVM.**
  `interfaceOverrideEdges` previously bridged interface methods to
  concrete impls in Java/Kotlin only. Now also runs for C#, TypeScript,
  JavaScript, Swift, and Scala — Swift conformance also iterates
  `struct` nodes (value-type protocol conformance) alongside `class`.
  Closes the same structural-typing gap the new Go gRPC bridge closes,
  for any language where the resolver emits explicit
  `implements`/`extends` edges.
- **Shorter MCP tool descriptions.** All 10 `codegraph_*` tool
  descriptions condensed (typically ~50% shorter), keeping the
  "use this for X / prefer over Y" steering but dropping the longer
  rationale (which lives in `server-instructions.ts`, the
  load-bearing channel). Tool-list bytes on the agent side drop
  proportionally; cumulative across multi-tool sessions.
- **Java / Kotlin imports now resolve by fully-qualified name.** Extraction
  wraps every top-level declaration of a `.kt` / `.java` file in a `namespace`
  node carrying the file's `package` (so a class `Bar` in
  `package com.example.foo` is indexed with qualifiedName
  `com.example.foo::Bar`), and `import com.example.foo.Bar` looks the target
  up through that index — regardless of whether the class lives in `Bar.kt`,
  `Models.kt`, or a top-level function. Disambiguates same-name classes
  across packages (the central failure mode of the previous name-matcher
  fallback in multi-module Spring / Android codebases), works across the
  Java↔Kotlin interop boundary, and lays groundwork for binding-precise
  Dagger2 / Hilt resolution. Wildcard imports (`com.example.*`) still go
  through name-matcher.
- **Java / C# anonymous classes (`new T() { ... }`) are now extracted as
  first-class class nodes with their overrides.** Previously, an anonymous
  subclass returned from a factory or lambda — `return new BaseIter() {
  @Override int separatorStart(int s) { ... } };` — produced only an
  `instantiates` edge: the override methods were invisible to the graph and
  Phase 5.5 interface-impl synthesis had no class to bridge. The anon class
  now lands as `<TypeName$anon@line>` with an `extends` reference to the
  named base/interface, scoped under the enclosing method, and its
  `method_declaration` members become normal method nodes. The interface→impl
  synthesizer then bridges the base's abstract methods to the anonymous
  overrides automatically. Concrete effect on `google/guava` (3,227 .java
  files): 3,608 anonymous classes extracted, +2,534 interface-impl edges
  reach overrides hidden in `new T() { ... }` blocks (including lambda
  bodies). An agent investigating `Splitter.SplittingIterator.separatorStart`
  now sees the four anonymous overrides in its trail without a Read.

### Changed
- **The installer no longer writes a `## CodeGraph` instructions block into
  your agent's instructions file** (`CLAUDE.md`, `AGENTS.md`, `GEMINI.md`,
  Cursor's `.cursor/rules/codegraph.mdc`, or Kiro's steering doc). That block
  duplicated, almost verbatim, the usage guidance the MCP server already
  emits in its `initialize` response — so every agent that surfaces MCP
  instructions (Claude Code does) read the same playbook twice each turn
  (#529). The MCP server instructions are now the single source of truth.
  `codegraph install` stops writing the block, and **the next time you run
  `codegraph install` (or `codegraph uninstall`) it strips a block a previous
  version wrote**, preserving everything else in the file (and deleting Cursor
  `.mdc` / Kiro steering files that were ours outright). Note: simply upgrading
  the npm package does not remove an existing block — re-run the installer to
  clean it up. The leftover block is harmless meanwhile (just redundant with
  the MCP instructions). If you'd added your own notes inside the
  `<!-- CODEGRAPH_START -->`/`<!-- CODEGRAPH_END -->` markers, move them outside
  the markers first — only the marked block is removed.

### Fixed
- **MCP tools no longer return rows for files deleted while no server was
  running.** The post-open catch-up sync that reconciles the index against
  the working tree (catching `git pull`/`checkout`/`rebase` and any edits
  or deletes made between sessions) was fire-and-forget — so a tool call
  that landed in the first ~50–300ms could race past it and serve rows
  for files that no longer exist on disk. The per-file staleness banner
  couldn't help here, because that signal is populated by the file
  watcher (which doesn't see pre-startup changes). Now the first tool
  call of the session awaits the catch-up before serving; subsequent
  calls pay nothing. Most visible on the "deleted everything between
  sessions" case, where MCP now returns the correct empty index instead
  of stale rows. Validated end-to-end on a 10,640-file VS Code index.
- **Windows: black console windows no longer flash on every file save / MCP
  reconnect (#485, #510, #530).** v0.9.5 moved the MCP server to a detached
  shared daemon (#411). Detached processes have no inherited console on
  Windows, so any console-subsystem child they spawn (the daemon's `git`
  invocations during auto-sync, the WASM-runtime `node` re-exec, the
  installer's `npm` shell-out) is created with a fresh console window
  visible to the user unless the spawn passes `windowsHide: true` (which
  libuv translates to `STARTF_USESHOWWINDOW | SW_HIDE`, so the window is
  created hidden and never flashes). All ten `spawnSync` / `execFileSync` /
  `execSync` call sites across extraction, sync, installer, and the
  WASM-flags relaunch now pass `windowsHide: true`. macOS/Linux ignore the
  option, so this is a no-op elsewhere. The daemon launcher itself
  (`src/mcp/index.ts`) already passed the flag — these children had been
  missed.
- **`codegraph index` / `init -i` summary now reports the true edge count.**
  The per-file counter in the orchestrator only saw extraction-phase edges,
  so resolution and synthesizer edges (often >50% of the graph on
  cross-file-heavy repos like Spring multi-module Java) were missing from
  the `X nodes, Y edges` line. Snapshotting the DB before/after the full
  pipeline now reports the actual additions. Example: indexing
  `macrozheng/mall` previously reported `20 047 edges` while the DB held
  `45 629`.

## [0.9.6] - 2026-05-27

- **C/C++ `#include` resolution — bare-basename includes now connect to the
  actual header file, not a phantom import node (#453).** Path-prefixed
  includes (`#include "common/args.h"`) already resolved via file-path
  suffix matching, but bare-basename includes (`#include "uint256.h"` from a
  caller in another directory) used to leave only a phantom edge to a
  floating `import` node owned by the including file. The resolver now walks
  C/C++ include search directories — pulled from `compile_commands.json`
  (`-I`/`-isystem` flags) when present, otherwise discovered by probing
  conventional dirs (`include/`, `src/`, `lib/`, `api/`, `inc/`) plus any
  top-level directory containing `.h`/`.hpp` files — and resolves the
  include to a real file node, producing a true file→file `imports` edge.
  System headers (`<stdio.h>`, `<vector>`, `<iostream>`, ~80 C and ~80 C++
  stdlib names) are filtered before the scan so they don't false-resolve
  via heuristic dir matching. C/C++ built-in symbols (`std::*` unconditionally,
  plus `printf`/`malloc`/`cout`/`make_shared`/etc. when **no user-defined
  symbol with that name exists**) are filtered from name-matching too —
  C/C++ projects routinely shadow stdlib names (custom allocators, stream
  wrappers, logging libs), so the filter only fires when there's no real
  definition to bind to. Measured on bitcoin-core (1,989 indexed files):
  C/C++ file→file `imports` edges 6,027 → 8,086 (**+34%**), false-positive
  call edges from `std::move`/`std::swap` etc. into similarly-named user
  methods −2,154 (**−3.6%** of C/C++ `calls`).
- **Enterprise Spring / MyBatis flow now traces end-to-end (#389).** Three gaps that previously forced agents back to grep on large Spring/MyBatis codebases are closed:
  - **MyBatis XML mapper indexing + Java↔XML bridge.** `*.xml` files containing `<mapper namespace="...">` are now first-class: each `<select|insert|update|delete id="X">` and `<sql id="X">` becomes a method-shaped node qualified as `<namespace>::<id>`, and a new synthesizer (`mybatis-java-xml`) links the matching Java mapper interface method → its XML statement with a `calls` edge. `<include refid="...">` to a `<sql>` fragment in the same mapper also resolves. Non-mapper XML (`pom.xml`, `web.xml`, `log4j.xml`, etc.) emits just a file node — no symbol noise. Validated on macrozheng/mall-tiny: all 6 custom-SQL Java mapper methods reach their XML counterparts; `trace(UmsRoleController.listResource, UmsResourceMapper::getResourceListByRoleId-xml)` connects in 4 hops across controller → service-iface → impl → mapper-iface → XML.
  - **Spring `@Value`/`@ConfigurationProperties` config-key linkage.** `application.{yml,yaml,properties}` (+ profile variants `application-dev.yml`, `bootstrap.yml`, etc.) is parsed during indexing, with one `constant` node per leaf key qualified by its dotted path (`app.cache.name.user-token`). `@Value("${app.cache.name.user-token}")` and `@ConfigurationProperties(prefix = "app.cache")` references in Java/Kotlin emit binding nodes that resolve to the matching key (or, for `@ConfigurationProperties`, a key under the prefix). Spring's **relaxed binding** applies (kebab `cache-list` ↔ camel `cacheList` ↔ snake `cache_list` ↔ `CACHE_LIST`), so a Java `@Value("${app.retryCount}")` finds `app.retry-count` in `application.properties`. `${key:default}` form is supported; the default is stripped before lookup.
  - **Field-injected concrete-bean trace.** A Spring controller's `@Resource(name="userBO") private UserBO userbo;` followed by `this.userbo.toLogin2(...)` now resolves through to `UserBO.toLogin2` even when the field type is a concrete class whose name doesn't match the field by Java naming convention (`userbo` → `UserBO`). The fix is two layered changes in the language layer (Java only): (a) the call extractor unwraps `this.<field>` receivers (previously surfaced as `this.userbo.toLogin2` and dropped through every name-matcher strategy); (b) the resolver looks up the receiver name in the enclosing class's field declarations and uses the declared type to resolve the method. This generalizes beyond Spring — any Java code using `this.field.method()` now resolves correctly.

### Fixed
- **Java/Kotlin imports now disambiguate same-name classes across modules (#314).** A Maven multi-module project where `dao/converter/FooConverter` and `service/converter/FooConverter` both expose a `convert` method used to resolve via file-path proximity — picking whichever class was closer to the caller, which is wrong any time the caller lives in an equidistant cross-cutting module. The import resolver had no Java branch at all (`extractImportMappings` returned `[]` for `.java`/`.kt`), so the FQN signal Java imports carry — `import com.example.dao.converter.FooConverter;` — was being thrown away. New `extractJavaImports` parses regular and `import static` directives. `resolveViaImport` now has a Java/Kotlin cross-file branch that converts the imported FQN to a file-path suffix (`com/example/dao/converter/FooConverter.java`) and resolves the symbol against the file whose path matches. For the `@Autowired private FooConverter fooConverter; fooConverter.convert(...)` field-receiver pattern (Spring's typical shape), `matchMethodCall` now passes the imported FQN to `resolveMethodOnType` so when multiple `FooConverter::convert` candidates exist, the import — not iteration order — picks the right one. Validated end-to-end on a synthetic two-module repro: swapping only the `import` line on the caller (with identical field declaration and call site) switches the resolved target between dao and service correctly. On spring-petclinic, +15 newly import-resolved Java edges with no regression in `calls`/`imports`/`extends`.
- **TypeScript `type` aliases with object shapes no longer cause cross-module false-positive call edges (#359).** Receiver-typed `handle.stop()` where `handle: RecorderHandle` and `RecorderHandle = { stop: () => Promise<void> }` used to attach the call edge to an unrelated `class Foo { stop() {} }` in a sibling directory via path-proximity matching, because the type alias had no `stop` node — only the look-alike class did. The fix surfaces type-alias object-shape members (and intersection-type members) as first-class `property`/`method` nodes under the alias: `type X = { foo: T; bar(): T }` now produces `X::foo` and `X::bar` in the graph. Function-typed properties (`stop: () => Promise<void>`) are emitted as `method` kind so `obj.stop()` resolves to them; non-function properties remain `property` kind. With the alias's members in the graph, the existing camelCase receiver-name word overlap (`recorder` ↔ `RecorderHandle`) routes the call to the correct alias member instead of the wrong class. Anonymous nested object types inside generic arguments (`Promise<{ ok: true }>`) intentionally don't produce phantom members — only immediate `object_type` / `intersection_type` operands of the alias value are walked. Measured on excalidraw/excalidraw (314 .ts files): **+776 new property nodes** + **+1,008 method nodes from type-alias members** + **+226 newly accurate `calls` edges** pointing at alias members (some shifted from incorrect class targets, some previously unresolved).
- **C# now produces `references` edges for parameter, return, property, and field types (#381).** Indexing any C# project used to yield **zero** `references` edges, so `codegraph_callers SomeDto` returned no results even when the DTO was used as a parameter or return type across the codebase, and `codegraph_callees` on a service class only saw its `using` imports. Two root causes: `csharp.ts` was missing `returnField`, and the type-leaf walker only matched `type_identifier` nodes — but C# tree-sitter emits `identifier`/`predefined_type`/`qualified_name`/`generic_name` instead. The fix adds the missing extractor field, routes C# through a dedicated type walker that only descends into known type-position fields (so parameter NAMES like `request` in `Build(UserDto request)` never mis-emit as type refs), and hooks `extractField`/`extractProperty` to invoke the walker. Measured on dotnet/eShop (527 `.cs` files): C# `references` edges go from **35 → 925** (+26x), with no regression in `calls`/`imports`/`instantiates`/`extends`/`implements`.
- **Go cross-package qualified calls (`pkga.FuncX(...)`) now resolve to the right package (#388).** On a Go monorepo with a layered package layout (handler/service/domain/dao), `codegraph_callers`, `_callees`, `_impact`, and `_trace` used to return ~0-1 results where grep finds hundreds to thousands of real call sites — the central value proposition of CodeGraph silently degraded on entire Go codebases. Root cause: the import resolver flagged every Go import path without `/internal/` as third-party (because it had no idea what the project's own module path was), so cross-package calls fell through to name-matching with path-proximity scoring, which on real codebases picks ~one accidental candidate per call site. The Go branch now reads the project's `go.mod`, treats `<module-path>/...` imports as in-module, and looks up the qualified symbol in the imported package's directory; same-name functions in *different* packages no longer collide. As a side fix, Go nodes now correctly carry `is_exported=1` for capitalized identifiers (the resolver needs this to filter candidates). Measured on gRPC-Go (1,031 `.go` files, layered packages): cross-package `calls` edges go from 10,880 → 19,929 (**+83%**), total `calls` from 23,803 → 34,105 (**+43%**), with no false-positive resolution of stdlib calls (`fmt.Println` etc. stay external).
- **`codegraph_files` now returns the whole project when an agent passes `path="/"`, `"."`, `"./"`, `""`, or a Windows-style `"\\"` — instead of "No files found matching the criteria."** Indexed file paths are stored as project-relative POSIX (e.g. `src/foo.ts`), but the path filter used a plain `startsWith`, so a leading slash or any of the other root-ish shapes an agent might guess matched nothing and pushed the agent back to Read/Glob — the exact opencode + Gemini Flash regression reported on Windows 11. Subdirectory filters are now equally forgiving: `"/src"`, `"./src"`, `"src/"`, `"src\\components"`, etc. all resolve correctly. Sibling-prefix bleed (`"src"` was previously matching `src-utils/...`) is also fixed — the filter now requires either an exact match or a `<filter>/` boundary. Closes #426.
- **File watcher no longer marks edited files as fresh when another process holds the index lock.** When a second writer (concurrent `codegraph index`, a git hook, another MCP daemon) held `.codegraph/codegraph.lock`, `CodeGraph.sync()` returned a zero-shape no-op instead of throwing. The file watcher took that as a successful sync and cleared `pendingFiles` — so the per-file staleness signal MCP tools surface to agents (issue #403) dropped immediately, even though the edit was never indexed. `CodeGraph.watch()` now converts that no-op into a typed `LockUnavailableError` thrown into the watcher; the existing retry path preserves `pendingFiles` and reschedules until the lock becomes available. The error is logged at debug only (no `onSyncError` callback) so a long-running external indexer doesn't spam stderr every debounce cycle. Closes #449.
- **TS/JS top-level initializer calls and inline-object-method calls are no longer dropped.** Calls inside a top-level variable initializer (`const token = getTokenMp()`) and inside methods of an inline object literal (`{ methods: { save() { getTokenMp() } } }`) were never walked by the variable / method-definition extractors, so `getTokenMp` showed up nowhere in `codegraph_callers`. The variable extractor now walks any non-object initializer value for calls; the method-definition extractor still avoids creating synthetic nodes for inline-object methods (the noise reason is unchanged) but now walks their bodies so the calls inside aren't lost. Surfaces in plain `.ts`/`.js` files (top-level `const x = foo()`) and in Vue SFCs (`<script setup>` initializers + classic Options API `methods: {...}` / `setup()`), where the bug was originally reported. Closes #425.
- **Watch sync no longer aborts with `FOREIGN KEY constraint failed`.** PR #62 plugged this FK violation at the extraction layer (empty-named nodes whose containment edges had no target), but the same violation kept reappearing on v0.9.5 during the daemon's *watch sync* — not on initial index. Once an agent's daemon had been running long enough to accumulate edits, a resolver lookup that crossed a framework-specific cache could hand back a node whose row had been removed by a recent file rewrite, and the FK check then aborted the entire resolution batch, leaving the user's daemon log filling with `Watch sync failed { error: 'FOREIGN KEY constraint failed' }`. `QueryBuilder.insertEdges` now validates every batch's endpoints against the `nodes` table directly (one fresh `SELECT id IN (...)` per batch, no cache) and silently skips edges with missing source or target — so a stale lookup result drops one edge instead of aborting the whole sync. Surfaces as a fresh `codegraph init`/`index` cycle now surviving its first watch-sync cycle without the FK error, and the daemon recovering naturally instead of compounding into further failures. Closes #455.
- **Hermes Agent: `codegraph install --target hermes` no longer corrupts `~/.hermes/config.yaml`.** Hermes serializes its config with PyYAML's default block style, which writes list items at the *same* indent as the parent mapping key (`cli:` and `- hermes-cli` both at column 2). The previous line-based YAML patcher mistook that first `  - hermes-cli` for the next sibling key, truncated the `cli:` block, and then spliced `- mcp-codegraph` at indent 4 *before* the existing items — leaving subsequent entries (`- browser`, `- clarify`, …) and even other platforms (`telegram:`, `discord:`) appearing at the `platform_toolsets:` level, which is no longer parseable YAML. The installer now recognizes the same-indent list style, finds the real end of the block at the next sibling key, and appends `- mcp-codegraph` at whatever indent the existing items already use. Re-installing on an already-corrupted file (or a 4-space-nested config that worked before) still produces a clean, parseable result. Closes #456.
- **NestJS: `RouterModule.register([...])` route prefixes now propagate to controller routes.** Previously a controller declared inside a module wired through NestJS's `RouterModule` (a common pattern for modular apps with nested route prefixes) was indexed with its raw `@Controller(...) + @Get(...)` path — so `UsersController` under `RouterModule.register([{ path: 'admin', module: AdminModule, children: [{ path: 'users', module: UsersModule }] }])` showed up as `GET /` instead of `GET /admin/users`. The new cross-file pass walks every `*.module.{ts,js}` for `RouterModule.register/forRoot/forChild([...])` (recursive `children`) and `@Module({ controllers: [...] })`, then prepends the correct prefix to each affected route — including non-empty `@Controller` paths and method-level params (`/admin/users/:id`). The route node's `id` is preserved across the update so existing route→handler edges stay intact, and the pass is idempotent so incremental sync recovers when `app.module.ts` itself is edited. Closes #459.
- **C++ callers now resolve through typed member pointers (#445/#454).** `codegraph callers CDetect::Processing` previously returned nothing for call sites like `m_cpAlg->Processing()` because (a) `field_expression` calls weren't kept as receiver-qualified references, (b) out-of-line method definitions (`int CDetect::Processing() {...}` in `.cpp` while the class is in `.hpp` — typical C++ layout) weren't surfaced as class methods, and (c) the resolver had no way to bridge a `Type* receiver` declaration to its method calls. Calls through typed object pointers, references, and stack values now resolve to the right class's method, including the common ambiguous-name case (two classes with a shared method name) and call sites embedded in `return ptr->m()` or `Type x = ptr->m()` forms. Measured on bitcoin-core (1306 .cpp files): +6.1% C++ caller edges resolved end-to-end.

### Added
- **Installer targets for Gemini CLI and the Antigravity IDE.** `codegraph install` (and the interactive prompt) now detect and configure two more agents out of the box:
  - **Gemini CLI** (also covers the rebranded Antigravity CLI) — writes `mcpServers.codegraph` to `~/.gemini/settings.json` (global) or `./.gemini/settings.json` (local), and the codegraph usage block into `~/.gemini/GEMINI.md` / `./GEMINI.md`. Existing top-level settings (e.g. `security.auth`) and sibling MCP servers are preserved.
  - **Antigravity IDE** — writes `mcpServers.codegraph` to Antigravity's unified MCP config at `~/.gemini/config/mcp_config.json` (post-migration, signalled by the `.migrated` marker Antigravity itself drops). Falls back to the legacy `~/.gemini/antigravity/mcp_config.json` for users on a pre-migration Antigravity build. On install, a stale codegraph entry in the legacy path is migrated to the new file automatically. Uninstall sweeps both. Antigravity-managed sibling fields (e.g. the `"disabled": true` flag the IDE adds when a user disables a server through the UI) are preserved across re-installs.
  - The Antigravity entry omits the `type: "stdio"` field the other targets use — Antigravity rejects entries that carry it.
  - On macOS, the Antigravity entry resolves `codegraph` to its absolute path at install time (e.g. an nvm-managed `~/.nvm/.../bin/codegraph`). macOS GUI apps launched from Dock/Finder get a stripped PATH that doesn't include nvm, so a bare command name fails to spawn — even when `which codegraph` works in your shell. Linux GUI apps inherit user PATH and Windows uses env `PATH` directly, so both keep the bare command.
  - The IDE shares `GEMINI.md` with Gemini CLI, so the two targets compose naturally when both are installed; the antigravity target deliberately doesn't touch `GEMINI.md` so uninstalling Antigravity alone leaves CLI instructions intact.

  Both targets are tested on the same parameterized contract as the existing five agents (idempotent install, sibling preservation, install/uninstall round-trip), with extra coverage for migration-marker detection, legacy → unified entry migration, sibling `disabled` field preservation, and the cross-target case where Gemini CLI and Antigravity IDE coexist in the same `~/.gemini/`. Closes #399.
- **Installer target for Kiro (CLI + IDE).** `codegraph install` now detects and configures Kiro out of the box on macOS, Linux, and Windows. Writes `mcpServers.codegraph` to `~/.kiro/settings/mcp.json` (global) or `./.kiro/settings/mcp.json` (local), and the codegraph usage block into a dedicated `~/.kiro/steering/codegraph.md` / `./.kiro/steering/codegraph.md` — Kiro's steering system loads every `*.md` file in `steering/` as agent context, so a dedicated file is the natural surface (no marker-based merging required). Sibling MCP servers in `mcp.json` and unrelated steering files (`product.md`, `tech.md`, etc.) are preserved across install / uninstall. Tested on the same parameterized contract as the other agent targets (idempotent install, sibling preservation, install/uninstall round-trip). Closes #385.
## [0.9.5] - 2026-05-25

### Added
- **Shared MCP daemon — running multiple AI agents in the same project no
  longer multiplies the file-watch, SQLite, and indexing cost.** Point more
  than one `codegraph serve --mcp` at a project (two Claude Code windows, an
  agent in a git worktree, `/loop` alongside an interactive session, parallel
  sub-agents) and they now share **one** background daemon per project: a
  single file watcher (one inotify set on Linux), one SQLite connection, and
  one tree-sitter warm-up — instead of N independent copies. Measured on Linux:
  three agents register **~3× fewer inotify watches** sharing one watcher
  versus three standalone servers. Resolves issue #411. (Composable with the
  per-watcher pruning in #276/#346 — that shrinks each watch set; this shares
  one across agents.)
- The daemon runs as a **detached background process** that outlives any single
  session, so closing one editor or terminal never severs the others. Each
  `serve --mcp` your agent host launches is a thin stdio↔socket proxy to it (a
  Unix-domain socket, or a named pipe on Windows). When the last client
  disconnects the daemon lingers for `CODEGRAPH_DAEMON_IDLE_TIMEOUT_MS`
  (default `300000`) so back-to-back sessions skip the startup cost, then exits
  and removes its lockfile — an OOM-killed or force-quit host can't leak it.
- **`CODEGRAPH_NO_DAEMON=1`** opts out, restoring one independent server per
  client (handy for debugging or sandboxes that disallow local IPC sockets).
  The daemon is also version-pinned: after you upgrade codegraph, sessions
  already attached to the old daemon keep using it while new sessions run
  standalone until it idles out — they never mix versions over the socket.

- **Per-file staleness banner — codegraph responses now tell the agent which
  files are pending re-index (#403).** When the file watcher has seen edits
  since the last successful sync, MCP tool responses (`codegraph_search`,
  `context`, `callers`, `callees`, `impact`, `trace`, `explore`, `node`,
  `files`) prepend a `⚠️` banner naming the stale files referenced in that
  response, with their edit age and indexing state; pending files elsewhere in
  the project appear as a small footer. The agent is told which specific files
  to Read directly; the rest of the response is fresh and codegraph stays
  authoritative for it. No artificial wait, no static "wait ~500ms" guess —
  the cost is zero when nothing's pending. `codegraph_status` also surfaces a
  `### Pending sync:` section so an agent can ask "is the index caught up?" in
  one call.
- **`CODEGRAPH_WATCH_DEBOUNCE_MS` env var lets you tune the file-watcher quiet
  window (#403).** Default stays at 2000ms; workspaces with bursty writes
  (formatter-on-save chains, multi-file refactors, large generated outputs)
  can raise it (e.g. `5000` or `10000`) without touching their agent's command
  line. Clamped to `[100ms, 60s]`; out-of-range or non-numeric values fall
  back to the default and the active value is logged to stderr on watcher
  startup so it's discoverable. Pairs with the staleness banner above: the
  banner stays accurate at any debounce value because it's per-file, not a
  static "wait N ms" instruction.

- **Objective-C indexing — `.m`, `.mm`, and content-sniffed `.h` files now
  parse with full structural extraction (#165).** Adds a tree-sitter-objc
  extractor that produces `class` nodes for `@interface` / `@implementation`
  (deduplicated into one), `protocol` nodes for `@protocol`, methods with
  **full multi-part selectors** (`setObject:forKey:`, `tableView:didSelectRowAtIndexPath:`
  — not just the first keyword, which would collide distinct methods),
  `+`/`-` static distinction, `@property` declarations, `#import` for both
  `<system>` and `"local"` forms, and `extends` / `implements` edges for
  superclasses and `<Protocol>` conformance lists. Call edges come from
  both C-style `call_expression` and ObjC `message_expression` (with
  `self`/`super` skipped on qualified callee names). Header files default
  to C unless content-sniffing finds `@interface`/`@implementation`/
  `@protocol`/`@synthesize`, so iOS headers classify correctly without
  breaking pure-C projects. Validated on AFNetworking (84 files, 100% file
  coverage, 93 multi-keyword selectors), RestKit (282 files, 99.6%), and
  Texture (926 files, 100% — including heavy `.mm` ObjC++ content).

  Disclosed limitations: categories produce one extra class node per
  category file (e.g. `ASDisplayNode+Yoga.m` creates a second `ASDisplayNode`
  node attributed to the category file); chained/nested message sends record
  only the innermost method; `[Class alloc]` patterns don't yet emit
  `instantiates` edges; `@protocol Foo <Bar>` refinement lists aren't wired
  to `implements`; heavy C++ in `.mm` files may parse incompletely under the
  ObjC grammar. Mixed Swift/Objective-C cross-language resolution
  (`@objc`-exposed Swift methods, bridging headers, React Native's native
  bridge) is **not** in scope for this entry — that's a separate effort
  tracked under the dynamic-dispatch coverage playbook.

- **Mixed iOS, React Native, and Expo cross-language bridging.** Real iOS
  and React Native codebases live across multiple languages — a Swift caller
  invokes an Objective-C selector that's been auto-bridged, JS calls into a
  native module via the React Native bridge, JSX delegates to a native view
  manager. Static tree-sitter extraction stops at each boundary. CodeGraph
  now bridges them so `trace` / `callers` / `callees` / `impact` connect
  end-to-end across the gap. Closes the iOS/RN parts of the request thread
  for #401. Bridges added:

  - **Swift ↔ Objective-C.** Swift `@objc` auto-bridging rules
    (`func play(song:)` ↔ ObjC `-playWithSong:`, `init(name:, age:)` ↔
    `-initWithName:age:`, `var x: T` ↔ `-x`/`-setX:`, `@objc(custom:)`
    overrides) plus the Cocoa preposition-prefix forms that reverse-import
    natively (`objectForKey:`, `stringWithFormat:`, etc.). Validated on
    Charts (28 / 1 bridge edges objc→swift / swift→objc), realm-swift
    (36 / 1185), wikipedia-ios (52 / 983). The high-confidence direction
    is ObjC→Swift, since Swift callsites carry the bare method name only
    and many overlap with Cocoa built-ins.

  - **React Native legacy bridge + TurboModules.** Parses
    `RCT_EXPORT_MODULE` / `RCT_EXPORT_METHOD` / `RCT_REMAP_METHOD` (ObjC
    & ObjC++) and `@ReactMethod` (Java/Kotlin) declarations; treats
    `Native<X>.ts` TurboModule spec files as ground truth. A JS callsite
    of `NativeModules.X.fn(...)` or `import X from './NativeX'; X.fn(...)`
    resolves to the matching native method. Validated on AsyncStorage
    (8/8 precise), react-native-svg (9 TurboModule bridges to Java),
    react-native-firebase (18 precise after `RCTEventEmitter` built-in
    blocklist).

  - **Native → JS event channel.** Synthesizes cross-language edges
    keyed by literal event name: ObjC `sendEventWithName:@"X"` /
    Swift `sendEvent(withName: "X", ...)` / Java/Kotlin `.emit("X", ...)`
    → JS `new NativeEventEmitter(...).addListener("X", handler)`.
    Falls back to attributing the JS endpoint to an enclosing
    `constant`/`variable` for the very common
    `const Foo = { watchX(listener) { ... addListener('X', listener) } }`
    wrapper-API pattern. Validated on RNFirebase (3 push-notification
    flow edges) and RNGeolocation (2 location-event edges).

  - **Expo Modules.** Parses Swift/Kotlin Expo DSL —
    `Module { Name("X"); Function("y") { ... }; AsyncFunction("z") { ... };
    Property("w") { ... } }` — and synthesizes `method` nodes named after
    each declaration. JS callsites of `requireNativeModule('X').y(...)`
    then resolve via existing name-match. Validated on expo-haptics
    (6 method nodes across Swift + Kotlin), expo-camera (41 covering the
    full SDK surface), and a 7-package Expo sweep (134 method nodes).

  - **Fabric / Codegen + legacy Paper view components.** Parses TS
    `codegenNativeComponent<NativeProps>('Name', ...)` Codegen specs AND
    legacy `RCT_EXPORT_VIEW_PROPERTY` / `@ReactProp` view-manager
    macros. Emits a `component` node per declaration and a `property`
    node per declared prop, then a synthesizer links the component to
    its native impl class by convention-based name+suffix
    (`View`/`ComponentView`/`Manager`/`ViewManager`). The existing JSX
    synthesizer then connects consumer JSX `<MyView/>` → component →
    native class. Validated on react-native-segmented-control
    (legacy Paper — 1 component, 11 props, 4 bridges),
    react-native-screens (Codegen Fabric — 27 components, 272 props,
    68 bridges), and react-native-skia (hybrid, monorepo — 5 components,
    14 props, 15 bridges across Codegen TS specs + Android Java
    ViewManagers + iOS ObjC).

  Each bridge emits `provenance:'heuristic'` edges with a stable
  `metadata.synthesizedBy:` channel name (`swift-objc-bridge`,
  `react-native-bridge`, `rn-event-channel`, `fabric-native-impl`,
  `expo-modules`) so an agent can tell at a glance how a cross-language
  hop got into the graph. Per-bridge precision blocklists prevent
  noisy over-linking on generic Cocoa names (`init`, `description`,
  `count`, …) and RN event-emitter built-ins (`addListener`, `remove`,
  …) that every NSObject / RCTEventEmitter subclass exposes.

  Architectural fix surfaced during validation: the resolver's
  `initialize()` runs at CodeGraph construction (before any files are
  indexed), so framework resolvers whose `detect()` consults the
  indexed file list silently dropped themselves. `indexAll()` now
  re-initializes the resolver after extraction so all frameworks see
  the populated index — a pre-existing latent bug that also affected
  the UIKit and SwiftUI resolvers.

  Out of scope for this round: bare JSI (non-TurboModule), dynamic
  bridge keys (`NativeModules[someVar]`), Android-Java extraction
  improvements beyond name-match (we use whatever the existing Java
  extractor produces). Anti-goals documented in
  `docs/design/mixed-ios-and-react-native-bridging.md`.

### Fixed
- **TypeScript interface members now produce `references` edges to their
  annotated types (#432).** Types that appeared only in an interface's
  property or method signatures — e.g. `value?: Partial<IPage>` or
  `fetchPage(arg: IPage): IOrderField` — were being silently dropped at
  extraction time, so `codegraph_impact`/`codegraph_callers` on the named
  type missed every consumer that imported it just to use it in an
  interface shape. The walker now extracts type annotations from both
  `property_signature` and `method_signature` nodes inside class-like
  parents (interfaces, classes), and the resolver wires the resulting
  references the same way it wires field and parameter types elsewhere.
- **Git worktrees no longer silently borrow another tree's index (#155).**
  When a worktree is nested inside the main checkout — exactly what agent
  tools that place worktrees under gitignored paths like
  `.claude/worktrees/<name>/` do — running CodeGraph from that worktree used
  to walk *up* to the main checkout's `.codegraph/` and silently return that
  tree's code (usually a different branch). Symbols changed only in the
  worktree were invisible and nothing told you. Now `codegraph status` (CLI +
  MCP) calls out the conflict explicitly, and every MCP read tool
  (`codegraph_search`/`context`/`trace`/`callers`/`callees`/`impact`/
  `explore`/`node`/`files`) prefixes a one-line notice naming the borrowed
  index and the fix (`codegraph init -i` in the worktree). Detection is
  best-effort (no git / not a repo / monorepo subdir → no warning) and runs
  once per session per start path, so it never costs more than a single pair
  of `git rev-parse` invocations.
- **The file watcher no longer exhausts the OS file-watch budget on large
  repos (#276).** It used to register a recursive watch over the *entire*
  project — `node_modules/`, build output, caches and all — and filter only
  after the fact. On Linux that meant hundreds of thousands of inotify watches
  per project; enough that a second project, or codegraph alongside your editor
  / `next dev`, could hit the per-user ceiling and fail with "OS file watch
  limit reached." The watcher now excludes the same directories the indexer
  ignores (the built-in default-ignore set **plus** your `.gitignore`) *before*
  registering a watch — so on a repo with a 900-directory `node_modules` the
  watch count drops from ~1,200 to ~14, even when the project has no
  `.gitignore`. (Stacks with the shared daemon from #411: one watcher across
  agents, and now that watcher is small.)
- **The index now stays in sync after `git pull`, branch switches, and edits made
  outside your editor.** Incremental sync detected changes via `git status`, which
  only sees *uncommitted* edits — so code pulled or checked out (which leaves a
  clean working tree) was silently missed until a full `codegraph index -f`.
  Change detection is now filesystem-based and git-independent: a `(size, mtime)`
  stat pre-filter skips unchanged files, then a content hash confirms the rest. It
  reconciles committed changes from `pull`/`checkout`/`merge`/`rebase`, plain edits
  in non-git projects, and deletions alike.
- **The MCP server catches up on connect.** When your editor connects, codegraph
  reconciles anything that changed while it wasn't running (e.g. a `git pull` from
  the terminal), so the first query reflects the current code instead of a stale
  snapshot — rather than waiting for the next live edit.
- **Dependency, build, and cache directories are now excluded by default** —
  `node_modules`, `vendor`, `dist`, `build`, `target`, `.venv`, `__pycache__`,
  `Pods`, `.next`, and the like across every supported language/framework — so
  `context` and `search` reflect your code instead of third-party noise, even in a
  project with no `.gitignore` (#407). The defaults apply uniformly, including to
  committed files (vendoring a dependency into the repo doesn't make it project
  code). To index one anyway, add a `.gitignore` negation (e.g. `!vendor/`).
  First-party-prone names like `packages/`, `lib/`, `app/`, and `src/` are never on
  the default list.

## [0.9.4] - 2026-05-24

### Added
- **Framework-aware route resolution — `request → route → handler → service`
  flows now resolve end-to-end across the supported stacks.** Added or fixed
  routing for Express (inline arrow handlers → services), Rails, Spring (Java +
  Kotlin; bare and class-prefixed mappings), Django/DRF (`router.register` →
  ViewSet), Laravel (`Controller@method`), Flask/FastAPI (decorator stacks,
  empty-path routers, Flask-RESTful `add_resource`), Gin/chi (group-var routing),
  ASP.NET (feature-folder + bare attribute routes), Drupal, Rust (Axum chained
  methods, actix builder API), Vapor (Swift grouped routes), Play (`conf/routes`),
  Vue/Nuxt SFC templates, Svelte/SvelteKit, and React Router (`<Route>` JSX +
  object data-router).
- **Dynamic-dispatch flow synthesis — `codegraph_trace`, `codegraph_callees`, and
  `codegraph_explore` now follow flows that have no static call edge.** Bridged
  channels: callback/observer registration, EventEmitter (`on`/`emit`), React
  re-render (`setState` → `render`) and JSX children, Flutter `setState` → `build`,
  C++ virtual overrides, and Java/Kotlin interface → implementation dispatch
  (e.g. Spring `@Autowired svc.list()` → the impl). Each synthesized hop is
  labeled inline in `trace` with where it was wired up.
- **`CODEGRAPH_MCP_TOOLS` — trim the exposed MCP tool surface.** Set it to a
  comma-separated list of tool names (e.g. `trace,search,node,context`) to expose
  only those codegraph tools over MCP; unset exposes all of them. Names match on
  the short form, so `trace` and `codegraph_trace` are equivalent. Lets you
  constrain an agent to a minimal surface (or A/B-test tool selection) without
  editing the client's MCP config. Inert by default.
- **Release archives now ship with a `SHA256SUMS` file**, and the npm launcher
  verifies the bundle it downloads against it — a mismatch aborts before anything
  runs. Releases published before this change have no checksum file, so the
  verification is skipped (not failed) when none is available.

### Changed
- **`codegraph_trace` now returns a self-contained flow dossier.** Each hop on
  the path is shown with its full body inline (previously just the call-site
  line), and the destination's own outgoing calls are appended — so one trace
  call usually answers a "how does X reach Y" flow question without a follow-up
  `codegraph_explore`/`codegraph_node`/Read. Measured across real repos: fewer
  tool calls and lower cost than the prior path-only output, with no wall-clock
  regression.
- **`codegraph_node` and `codegraph_trace` now emit line-numbered source**
  (`cat -n` style, matching `codegraph_explore` and Read), so an agent can cite
  or edit exact lines without re-reading the file just to recover line numbers.
- **`codegraph_explore` now leads with the execution flow** when its query names
  the symbols of a flow. Agents call `explore` far more than `trace`, passing a
  bag of symbol names that usually spans the flow they're investigating
  (`PmsProductController getList PmsProductService list PmsProductServiceImpl`);
  `explore` now finds the call path *among those named symbols* — riding
  synthesized dynamic-dispatch edges (callback / React re-render / JSX child /
  interface→impl) — and shows it first. So a flow question answered through
  `explore` gets the trace-quality path without the agent having to switch tools.
  Scoped to the named symbols (no wrong-feature wandering) and bridge-capped (no
  god-function fan-out); absent when the query is fuzzy or has no connected chain.

### Fixed
- **Static-extraction & resolution correctness fixes** underpinning the framework
  work above: C++ inheritance (`base_class_clause` was unhandled, so C++ `extends`
  edges were missing), Dart method body ranges (methods were extracted
  signature-only), a Python builtin-name handler guard (handlers named
  `index`/`get`/`update` were silently dropped), and an explore output-budget
  regression that under-returned source on god-file repos.
- **Orphaned `codegraph serve --mcp` processes after a parent SIGKILL.** When
  the MCP host (Claude Code, opencode, …) was force-killed — OOM killer, a
  `kill -9`, a container teardown — the child kept running indefinitely on
  Linux, holding inotify watches, file descriptors, and the SQLite WAL. The
  kernel doesn't propagate parent death to children, and the stdin
  `end`/`close` handlers we relied on don't always fire. The MCP server now
  polls `process.ppid` and shuts down the moment it changes from the value
  observed at startup; the poll interval is `CODEGRAPH_PPID_POLL_MS` (default
  `5000`, `0` disables). Resolves
  [#277](https://github.com/colbymchenry/codegraph/issues/277).

- **`codegraph: no prebuilt bundle for <platform>` after installing through a
  registry mirror.** Installing `@colbymchenry/codegraph` from a registry that
  hadn't mirrored the matching per-platform package — most often the
  npmmirror/cnpm mirrors, but any lazily-syncing mirror or corporate proxy can
  do it — left every command failing with `no prebuilt bundle for <platform>`.
  The runtime ships as a per-platform `optionalDependency`, and npm treats an
  optional package it can't fetch as a success and silently skips it, so the
  bundle simply went missing. The launcher now self-heals: when the platform
  bundle isn't installed, it downloads the same archive from GitHub Releases
  (cached under `~/.codegraph/bundles/` for next time) and runs that — so a
  global install works even on a mirror that never carried the platform package.
  Set `CODEGRAPH_NO_DOWNLOAD=1` to disable the network fallback, or
  `CODEGRAPH_DOWNLOAD_BASE=<url>` to point it at your own mirror of the release
  archives; the standalone `install.sh` remains the no-Node alternative. Resolves
  [#303](https://github.com/colbymchenry/codegraph/issues/303).
- **`install.sh` failing with `403` / "could not resolve latest version" on
  shared or cloud hosts.** The standalone installer resolved the latest release
  through the GitHub API, whose unauthenticated limit is 60 requests/hour per IP
  — routinely exhausted on cloud devboxes and CI where many users share an
  address, returning `403` (issue #325). It now resolves the version from the
  `releases/latest` web redirect, which isn't rate-limited (and still falls back
  to the API). `CODEGRAPH_VERSION` also accepts a bare `0.9.4` in addition to
  `v0.9.4`. Resolves
  [#325](https://github.com/colbymchenry/codegraph/issues/325).

## [0.9.3] - 2026-05-22

### Added
- **`codegraph uninstall` command.** Cleanly removes CodeGraph from every agent
  it's configured on — Claude Code, Cursor, Codex CLI, opencode, and Hermes
  Agent — in one step. It asks up front whether to remove the global config
  (`~/.claude`, `~/.codex`, …) or just this project's local config (no flags
  required), then prints exactly which agents it touched so you can see what
  changed. `--location`, `--target`, and `--yes` are accepted for scripted /
  non-interactive use. It removes only what `install` wrote (MCP server entry,
  instructions block, permissions) and leaves your `.codegraph/` index alone
  (use `codegraph uninit` for that). Resolves
  [#313](https://github.com/colbymchenry/codegraph/issues/313) — previously the
  only cleanup path was an npm `preuninstall` hook that the published bundle
  never shipped, so `npm uninstall -g` left every agent pointing at a CodeGraph
  MCP server that no longer existed.

### Fixed
- **`Fatal process out of memory: Zone` crash while indexing large projects.**
  On Node.js 22 and 24 — including CodeGraph's own bundled runtime — running
  `codegraph index` / `codegraph init` on a large multi-language repo could
  abort the entire process partway through parsing with
  `Fatal process out of memory: Zone`, even with tens of GB of RAM free (the
  failure is in a V8-internal compilation arena, not the JS heap). The cause is
  V8's "turboshaft" optimizing WASM compiler exhausting its Zone budget while
  compiling tree-sitter's large WebAssembly grammars on a background thread.
  CodeGraph now runs with V8's `--liftoff-only`, which keeps grammar compilation
  on the baseline compiler and never reaches the optimizing tier, eliminating
  the crash; indexing output is otherwise unchanged. The bundled launcher passes
  the flag directly, and any other launch path (from source, `npx`, a globally
  linked dev build) re-execs once with it automatically. Resolves
  [#298](https://github.com/colbymchenry/codegraph/issues/298) and
  [#293](https://github.com/colbymchenry/codegraph/issues/293). (Node 25 stays
  blocked — its variant of this V8 bug is not resolved by `--liftoff-only`.)
- **Cursor uninstall left an orphaned `.cursor/rules/codegraph.mdc`.** It
  stripped the rule body but left the file and its `description: CodeGraph …`
  frontmatter behind. The dedicated rules file is now deleted outright on
  uninstall, while any content you added outside CodeGraph's markers is kept.

## [0.9.2] - 2026-05-21

### Added
- **Installer target: Hermes Agent (Nous Research).** `codegraph install` now
  supports Hermes Agent — it writes the `mcp_servers.codegraph` entry and ensures
  `platform_toolsets.cli` includes `mcp-codegraph` in `$HERMES_HOME/config.yaml`,
  so Hermes can drive the CodeGraph knowledge graph like the other agents.
- **Framework support: Drupal 8/9/10/11** — CodeGraph now detects Drupal
  projects (via a `drupal/*` dependency in `composer.json`) and adds three
  levels of intelligence:
  - **Route extraction**: `*.routing.yml` files emit a `route` node per route,
    linked by a `references` edge to the `_controller`, `_form`, or
    entity-handler class/method, so querying a controller method surfaces the
    URL route that binds it.
  - **Hook detection**: hook implementations in `.module`, `.install`, `.theme`,
    and `.inc` files are detected via docblock (`Implements hook_X()`) with a
    module-name-prefix fallback. Each emits a `references` edge to the canonical
    `hook_X` name so `codegraph_callers("hook_form_alter")` returns every
    implementation across modules.
  - **Resolution**: `_controller`/`_form` FQCNs resolve to their PHP
    class/method nodes.
  New `yaml`/`twig` languages are tracked at the file level, the Drupal PHP
  extensions (`.module`/`.install`/`.theme`/`.inc`) are indexed with the PHP
  grammar, and `web/core`, `web/modules/contrib`, `web/themes/contrib` are
  excluded by default. Resolves [#268](https://github.com/colbymchenry/codegraph/issues/268).

### Changed
- **Zero-config indexing that respects `.gitignore`.** CodeGraph no longer has a
  config file. It indexes every file whose extension maps to a supported language
  and honors your `.gitignore` everywhere: in git repos via git itself, and in
  non-git projects (e.g. a freshly-scaffolded app before `git init`) by reading
  `.gitignore` files directly — root and nested, the same way git does (via the
  `ignore` library, so negation/anchoring/nested rules all behave correctly). To
  keep something out of the graph, add it to `.gitignore`. **Behavior change:**
  committed files that are *not* gitignored are now indexed even under `vendor/`,
  `Pods/`, or a committed `dist/` — previously a hardcoded exclude list skipped
  those names; now `.gitignore` is the single source of truth. Resolves
  [#283](https://github.com/colbymchenry/codegraph/issues/283).

### Fixed
- **Windows: `npm i -g @colbymchenry/codegraph` then any `codegraph` command
  failed with `spawnSync …\codegraph.cmd EINVAL`.** The npm launcher spawned the
  bundle's `.cmd` file directly, which modern Node refuses to do on Windows
  (the CVE-2024-27980 hardening — seen on Node 24). The launcher now invokes the
  bundled `node.exe` against the app directly, so `codegraph` works on Windows
  regardless of your Node version. Resolves
  [#289](https://github.com/colbymchenry/codegraph/issues/289).

### Removed
- **`.codegraph/config.json` and the entire config surface.** Every field was
  either inert or now redundant with `.gitignore`:
  - `languages`/`frameworks` never affected indexing (languages are detected per
    file from extensions; frameworks are auto-detected). `languages` was also
    broken — its validator only knew the original 8 languages, so setting it to
    anything newer (C#, PHP, Ruby, C/C++, Swift, Kotlin, Dart, Vue, Scala, Lua, …)
    threw `Invalid configuration format`.
  - `extractDocstrings`/`trackCallSites`/`customPatterns` were never read by any
    extractor.
  - `include` is now derived from the supported language extensions, `exclude` is
    replaced by `.gitignore`, and `maxFileSize` (1 MB) is a constant.

  **Breaking (library API):** the `CodeGraphConfig` type, the `config` option on
  `CodeGraph.init()`, and the `getConfig()`/`updateConfig()`/`getConfigPath`
  exports are gone. Existing `.codegraph/config.json` files are simply ignored.
  The `.codegraphignore` marker is no longer supported — use `.gitignore`.

### Security
- **MCP session marker no longer follows symlinks** (CWE-59). Every
  `codegraph_context` call writes a `codegraph-consulted-*` marker into the
  system temp dir; the previous write followed symlinks, so on a multi-user
  system another local user could pre-plant that path as a symlink and redirect
  the write onto a victim-writable file. The marker is now opened with
  `O_NOFOLLOW` and mode `0600`, and a planted symlink is refused rather than
  followed. Resolves [#280](https://github.com/colbymchenry/codegraph/issues/280).

## [0.9.1] - 2026-05-21

### Fixed
- **Standalone installers** (`curl … | sh`, `irm … | iex`): the bundled launcher
  failed with `exec: …/node: not found` because it didn't resolve the symlink the
  installer puts on your PATH. Installing on a machine with **no Node** now works.
- **npm**: `@colbymchenry/codegraph-linux-x64` is now published — the 0.9.0
  release silently shipped 6 of 7 packages, so `npm i -g` on linux-x64 couldn't
  find its bundle. The release pipeline now verifies every package reached the
  registry (and is idempotent), so a release can't pass green-but-broken again.

[0.9.5]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.5
[0.9.4]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.4
[0.9.3]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.3
[0.9.2]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.2
[0.9.1]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.1

## [0.9.0] - 2026-05-21

### 🎉 Self-contained: CodeGraph bundles its own runtime — install anywhere, on any Node (or none)

**No more `database is locked`. No more native build failures. No more "WASM fallback active."**

CodeGraph used to need `better-sqlite3`, a native module compiled against your exact
Node version. When that build failed (common on Windows and locked-down machines) it
silently dropped to a slow WASM SQLite build with **no WAL** — the root cause of the
intermittent `database is locked` errors on concurrent MCP tool calls
([#238](https://github.com/colbymchenry/codegraph/issues/238)). That entire class of
problem is **gone**: CodeGraph now ships a self-contained Node runtime and uses Node's
built-in `node:sqlite` (real SQLite, full WAL + FTS5).

- ✅ **Zero native compilation** — nothing to build, ever; nothing to rebuild when Node changes.
- ✅ **Runs on any Node version — or with no Node at all.** Install via the standalone installers with no Node present, or keep using `npm`/`npx` on any version (your Node only launches the bundled runtime).
- ✅ **`database is locked` fixed at the root** — real WAL means readers never block on a writer.
- ⚡ **5–10× faster** than the old WASM fallback for anyone who was stuck on it.

```bash
# macOS / Linux — no Node required
curl -fsSL https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.sh | sh
# Windows (PowerShell) — no Node required
irm https://raw.githubusercontent.com/colbymchenry/codegraph/main/install.ps1 | iex
# or, if you have Node (any version):
npm i -g @colbymchenry/codegraph
```

### Added
- **Standalone installers** — one-line install with no Node.js required:
  `curl -fsSL .../install.sh | sh` (macOS/Linux) and `irm .../install.ps1 | iex`
  (Windows). They fetch the matching self-contained bundle from GitHub Releases
  and put `codegraph` on your PATH.
- **Lua**: CodeGraph now indexes Lua (`.lua`) — functions, methods (table `t.f`
  and `t:m` definitions become methods with a `t::f` receiver-qualified name),
  local variables, `require(...)` imports, and the call edges between them.
  Querying a Lua project (Neovim plugins, Kong, OpenResty, game code) now
  surfaces its modules, methods, and call graph.
- **Luau** ([#232](https://github.com/colbymchenry/codegraph/issues/232)):
  CodeGraph now indexes Luau (`.luau`), Roblox's typed superset of Lua —
  everything Lua extracts, plus `type` / `export type` aliases, typed function
  signatures, generics, and Roblox instance-path `require(script.Parent.X)`
  imports.

### Changed
- **SQLite backend is now Node's built-in `node:sqlite`** (real SQLite, WAL +
  FTS5), shipped inside a bundled Node runtime. This fixes the concurrent-read
  `database is locked` errors ([#238](https://github.com/colbymchenry/codegraph/issues/238))
  at the root and removes the native build step entirely.
- **`npm i -g` / `npx` now install a self-contained bundle.** The main package is
  a tiny shim; the runtime ships as per-platform `optionalDependencies`, so the
  install works on any Node version (your Node only launches the bundle).
- **`codegraph status`** now reports the effective journal mode (`wal` vs not),
  so a `database is locked` report is triageable at a glance.

### Removed
- **`better-sqlite3`** (optional native dependency) and **`node-sqlite3-wasm`**
  (WASM fallback) — along with the native-build banner, the WASM fallback path,
  and the no-WAL lock retries they required. The dependency tree now has zero
  native addons.

### Fixed
- **Installer**: re-running `codegraph install` now removes the broken
  auto-sync hooks that pre-0.8 versions wrote to Claude Code's
  `settings.json`. Those builds added a `Stop → codegraph sync-if-dirty`
  hook (and a `PostToolUse → codegraph mark-dirty` partner); both
  subcommands were later removed from the CLI, so Claude Code reported
  `Stop hook error: ... unknown command 'sync-if-dirty'` on every turn.
  The cleanup is surgical — only codegraph's own hook entries are
  stripped, so unrelated hooks sharing the same file or event (e.g. a
  GitKraken `gk ai hook run` hook) are left untouched — and it also runs
  on uninstall, so the npm `preuninstall` step fully reverses a legacy
  install. Re-run `codegraph install` once on an affected machine to
  clear the error.

[0.9.0]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.0

## [0.8.0] - 2026-05-20

### Added
- **Framework routes (NestJS)**: CodeGraph now recognises NestJS projects and
  emits `route` nodes — each linked by a `references` edge to its handler
  method — across all four transport layers: HTTP controllers (the
  `@Controller` prefix joined with `@Get`/`@Post`/`@Put`/`@Patch`/`@Delete`/
  `@Head`/`@Options`/`@All`, including empty `@Controller()`/`@Get()`),
  GraphQL resolvers (`@Query`/`@Mutation`/`@Subscription`), microservice
  handlers (`@MessagePattern`/`@EventPattern`), and WebSocket gateways
  (`@SubscribeMessage`, prefixed with the gateway namespace). Detected
  automatically from any `@nestjs/*` dependency in `package.json`. Querying a
  controller method or resolver now surfaces the route that binds it.
  Resolves [#220](https://github.com/colbymchenry/codegraph/issues/220).
- **MCP / explore**: `codegraph_explore` source sections now carry line
  numbers (cat -n style `<num>\t<code>`, matching the Read tool). This lets
  the agent cite `file:line` straight from the explore payload instead of
  re-opening the file just to find a line number — the dominant residual
  cost on precise-tracing questions. In an isolated A/B (answer a
  "which exact line" question with the relevant code already in the
  payload), the no-line-numbers arm spent 2 file Reads + a grep recovering
  the line number while the line-numbered arm answered with zero follow-up
  tool calls. Payload cost is small (~3-5%). Set
  `CODEGRAPH_EXPLORE_LINENUMS=0` to disable.
- **MCP / watcher**: CodeGraph now skips the live file watcher on WSL2
  `/mnt/*` drives, where recursive `fs.watch` is slow enough to break MCP
  startup (see Fixed). When the watcher is off, `codegraph init` /
  `codegraph install` offer to keep the index fresh via git hooks
  (`post-commit`, `post-merge`, `post-checkout`) that run `codegraph sync`
  in the background — accept for automatic refresh on commit / pull /
  checkout, or decline and sync by hand. Either way you're told the index
  stays frozen until it's re-synced. New controls: `CODEGRAPH_NO_WATCH=1`
  (or `codegraph serve --mcp --no-watch`) forces the watcher off anywhere;
  `CODEGRAPH_FORCE_WATCH=1` overrides the WSL auto-detect when your `/mnt`
  setup is actually fast. `codegraph uninit` removes any hooks it installed.

### Changed
- **MCP / agent guidance**: CodeGraph now tells agents to answer "how does X
  work" / architecture questions *directly* — `codegraph_context`, then one
  `codegraph_explore` for the surfaced symbols — instead of delegating to a
  file-reading sub-agent or a grep+read loop. The server instructions and the
  installed instruction files (`CLAUDE.md`, `.cursor/rules/codegraph.mdc`,
  `AGENTS.md`) previously suggested *spawning a sub-agent* for explore-class
  questions, which produced the opposite, more expensive behavior: the
  sub-agent reads files regardless of the index, so CodeGraph became overhead
  stacked on top of the reads. In rigorous N≥4-per-arm benchmarks this cut the
  cost of an architecture question by ~42–47% versus a no-CodeGraph agent on
  medium and large repos (Excalidraw ~600 files, VS Code ~10k), with
  equal-or-better, `file:line`-cited answers and ~6× fewer tool calls; on a
  tiny repo (~25 files) it's a wash, since native grep is already trivially
  cheap there.
- **MCP / codegraph_node**: `includeCode=true` on a class/interface/struct/enum
  now returns a compact member outline (fields + method signatures + line
  numbers) instead of the entire class body — which could be thousands of
  characters and was rarely needed in full. Functions and methods still return
  their full body; request a specific member for its source.
- **Minimum Node.js is now 20** (was 18). Node 18 is end-of-life and the
  native SQLite binding (`better-sqlite3` 12.x) no longer ships a Node 18
  prebuilt binary. Node 22 LTS and Node 24 get the native backend out of the
  box; on other Node versions CodeGraph still runs via the WASM fallback
  (slower, but functional). Node 25+ remains blocked (V8 WASM JIT crash, see
  [#81](https://github.com/colbymchenry/codegraph/issues/81)).
- **MCP / explore**: `codegraph_explore` output is now adaptive to project
  size. The tool used to apply a fixed 35KB cap regardless of how large the
  codebase was, which on small projects (~100 files) produced bigger
  responses than the agent's native grep+Read flow would have — exactly the
  scenario reported in
  [#185](https://github.com/colbymchenry/codegraph/issues/185). The budget
  now scales with indexed file count: small projects (<500 files) cap at
  ~18KB and skip the "Additional relevant files" / completeness / explore-
  budget reminders that earn their keep on bigger codebases; medium
  (<5,000) caps at ~13KB; large (<15,000) keeps the historical ~35KB; very
  large goes up to ~38KB. A new per-file char cap also prevents a single
  file with many adjacent symbols from collapsing into one whole-file dump
  (the Alamofire `Session.swift` case from #185). Per-file cluster
  selection ranks clusters that contain a query entry point ahead of dense
  declaration blocks, and whole-file "envelope" nodes (a class/struct that
  spans most of the file) are excluded from clustering so the methods the
  query asked about aren't buried under the container's opening lines.
  Measured against the same repos used in the README benchmark, end state
  with line numbers on: Alamofire ~60% smaller per call, Excalidraw ~32%,
  VS Code ~12%. Agent-trust floor still holds — the Relationships section,
  scored cluster selection, and structured-source output are all retained.
  Thanks to [@essopsp](https://github.com/essopsp) for the repro.
- **Search ranking (Kotlin / Swift / Scala / C#)**: test files in these
  languages are now correctly de-prioritized in `codegraph_search`,
  `codegraph_context`, and `codegraph affected`. Detection previously only
  recognized `snake_case`/`.test.`-style names plus a handful of Java
  suffixes, so CamelCase test files (`FooTest.kt`, `BarTests.swift`,
  `BazSpec.scala`, `QuxTestCase.cs`) and Gradle / Kotlin-Multiplatform /
  Xcode test source-set directories (`jvmTest/`, `commonTest/`,
  `androidTest/`, `iosTest/`, `integrationTest/`) were treated as production
  code and could outrank the real implementation. Detection now matches
  capital-led `*Test` / `*Tests` / `*Spec` / `*TestCase` filenames and
  source-set directories — deliberately capital-led so lowercase look-alikes
  like `latest.kt` and `manifest.kt` are not misclassified.

### Fixed
- **MCP / explore**: `codegraph_explore` output is now hard-capped to its
  adaptive size budget. It could previously overrun (e.g. ~30K against a 28K
  cap) once the relationship map and trailer sections were appended; the
  oversized payload then sat in the agent's context and was re-read on every
  later turn.
- **Sync / status**: git-untracked files are no longer reported as pending
  "Added" forever. After `codegraph sync` indexed a newly-created untracked
  source file, `codegraph status` kept listing it under Pending Changes and
  every subsequent `sync` re-indexed it from scratch — even though its symbols
  were already queryable. Change detection trusted `git status` and counted
  every untracked (`??`) entry as new without checking the index, but indexing
  a file doesn't make git track it, so the file stayed `??` and got re-added on
  each run. CodeGraph now hash-compares untracked files against the index the
  same way it does tracked files: a file counts as "added" only if it's missing
  from the index, "modified" if its contents changed, and is skipped otherwise.
  Closes [#206](https://github.com/colbymchenry/codegraph/issues/206). Thanks to
  [@15290391025](https://github.com/15290391025) for the report.
- **Indexing**: `codegraph init -i` now finds source inside nested, independent
  git repositories — separate clones living inside the workspace that are **not**
  git submodules (common in CMake "super-repo" layouts). When the top-level
  workspace is itself a git repo, `git ls-files` reports an embedded repo only as
  an opaque `subdir/` entry and never lists its files, so indexing from the
  workspace root reported "No files found to index" even though indexing each
  sub-repo individually worked. CodeGraph now detects these embedded repos and
  indexes their tracked and untracked source, honoring each repo's own
  `.gitignore`. Closes
  [#193](https://github.com/colbymchenry/codegraph/issues/193). Thanks to
  [@timxx](https://github.com/timxx) for the report.
- **Native SQLite backend on Node 24**: indexing on Node 24 always dropped to
  the 5-10x-slower WASM backend, printing a `better-sqlite3 unavailable`
  warning that `npm rebuild better-sqlite3` / `xcode-select --install` could
  not clear ([#203](https://github.com/colbymchenry/codegraph/issues/203)).
  The bundled `better-sqlite3` was pinned to a v11 release that ships no
  prebuilt binary for Node 24's ABI (`node-v137`), so every Node 24 install
  silently degraded — and because CodeGraph is usually installed globally, the
  `npm install` / `npm rebuild` people ran in their own project never touched
  CodeGraph's copy. CodeGraph now requires `better-sqlite3` `^12.4.1`, whose
  prebuilds include Node 24, so a fresh install on Node 22 or Node 24 gets the
  native backend with no compiler. On an already-broken install, reinstall
  CodeGraph (e.g. `npm install -g @colbymchenry/codegraph`) to pull the new
  binding; `codegraph status` should then report `Backend: native`. Thanks to
  [@Finndersen](https://github.com/Finndersen) for the report.
- **MCP**: tools no longer fail with "CodeGraph not initialized" when the index
  actually exists. This hit clients that launch the MCP server from a directory
  other than your project and don't report a workspace root in `initialize`
  (some IDE/JetBrains-family integrations) — the server fell back to its own
  working directory, missed the project's `.codegraph/`, and returned the
  misleading "Run 'codegraph init' first" on every call. The only workaround
  was passing `projectPath` to each tool by hand. Now, when no project path is
  supplied, the server asks the client for its workspace root via the standard
  MCP `roots/list` request (when the client advertises the `roots` capability)
  before falling back to the working directory — so detection just works for
  spec-compliant clients. When it still can't resolve a project, the error is
  now actionable: it names the directory it searched and tells you to pass
  `projectPath` or add `--path /abs/project` to the server's MCP config args,
  instead of pointing you at a re-init you don't need. Closes
  [#196](https://github.com/colbymchenry/codegraph/issues/196). Thanks to
  [@zhangyu1197](https://github.com/zhangyu1197) for the report and the
  `projectPath` workaround.
- **MCP**: the server no longer hangs on startup under WSL2 when the project
  lives on an NTFS `/mnt/*` mount. Setting up the recursive file watcher
  there took tens of seconds — every directory read crosses the Windows/9p
  boundary — which blew past the host's initialization timeout (opencode's
  30s), so the codegraph tools silently never appeared, even on small
  projects. This is the file-watcher half of the
  [#172](https://github.com/colbymchenry/codegraph/issues/172) startup fix:
  that one moved the database/WASM open off the handshake, but the watcher
  setup was still on the critical path. CodeGraph now auto-skips the watcher
  on those mounts, with manual and git-hook sync fallbacks (see Added).
  Closes [#199](https://github.com/colbymchenry/codegraph/issues/199).
  Thanks to [@mengfanbo123](https://github.com/mengfanbo123) for the precise
  root-cause analysis and workaround.
- **Installer (Claude Code)**: project-local installs (`Just this project`)
  now write the MCP server to `.mcp.json` in the project root — the file
  Claude Code actually reads for project-scoped servers. Previously they
  wrote `.claude.json`, which Claude Code ignores, so the codegraph tools
  silently never appeared and you had to rename the file by hand to make it
  work. Re-running `codegraph install` (or `codegraph init`) on an affected
  project migrates the stale `.claude.json` entry into `.mcp.json`
  automatically; uninstall cleans up both. Global (`All projects`) installs
  were unaffected — they correctly target `~/.claude.json`. Closes
  [#207](https://github.com/colbymchenry/codegraph/issues/207). Thanks to
  [@Jhsmit](https://github.com/Jhsmit) for the report and the workaround.
- **MCP**: source-omission markers in `codegraph_explore` and
  `codegraph_context` output are now language-neutral (`... (gap) ...`,
  `... (trimmed) ...`, `... (truncated) ...`) instead of C-style `//`
  comments, which were misleading inside Python, Ruby, and other non-C
  fenced source blocks.

## [0.7.10] - 2026-05-19

### Fixed
- **MCP**: tools no longer silently fail to appear in clients on slow
  filesystems (Docker Desktop VirtioFS on macOS, WSL2). The `initialize`
  handshake was blocking on opening the SQLite database and bootstrapping
  the tree-sitter WASM runtime, which on slow I/O could exceed Claude
  Code's ~30s handshake timeout — leaving the codegraph process alive but
  unresponsive and no tools visible. The handshake now returns immediately
  and defers project open to the background; tool calls wait on the
  in-flight init rather than racing it with a second open. Closes
  [#172](https://github.com/colbymchenry/codegraph/issues/172). Thanks to
  [@sashanclrp](https://github.com/sashanclrp) for the original report and
  detailed reproduction, and [@sgrimm](https://github.com/sgrimm) for the
  decisive wire capture that isolated the actual root cause.
- **CLI**: terminal output no longer mojibakes on Windows PowerShell /
  cmd.exe during `codegraph index` and `codegraph sync`. The shimmer
  progress renderer writes from a worker thread via `fs.writeSync(1, …)`
  to keep the animation smooth while the main thread is busy in SQLite,
  which bypasses Node's TTY-aware UTF-8→codepage conversion — so glyphs
  like `│ ◆ —` were emitted as raw UTF-8 bytes and reinterpreted as the
  console's OEM codepage (CP437, CP936, …), producing strings like
  `鋍?[0m 鉒?[0m Scanning files 鈥?N found`. CodeGraph now picks an ASCII
  glyph set on Windows by default (`| * -` instead of `│ ◆ —`); set
  `CODEGRAPH_UNICODE=1` to opt back into the Unicode glyphs (e.g. on
  pwsh 7 with UTF-8 codepage), or `CODEGRAPH_ASCII=1` on any platform to
  force ASCII (useful for log collectors / non-TTY pipelines). Closes
  [#168](https://github.com/colbymchenry/codegraph/issues/168). Thanks to
  [@starkleek](https://github.com/starkleek) for the report and to
  [@Bortlesboat](https://github.com/Bortlesboat) for the initial PR.
- **MCP / search**: module-qualified symbol lookups now resolve. The
  MCP tools (`codegraph_node`, `codegraph_callees`, `codegraph_impact`,
  …) accept `module::symbol` (Rust / C++ / Ruby), `Module.symbol`
  (TS / JS / Python), and `module/symbol` (path-style) — multi-level
  forms (`crate::configurator::stage_apply::run`) and Rust path
  prefixes (`crate`, `super`, `self`) are handled. Closes
  [#173](https://github.com/colbymchenry/codegraph/issues/173). Thanks
  to [@joselhurtado](https://github.com/joselhurtado) for the detailed
  reproduction. Three underlying fixes:
    - The FTS5 query builder now treats `::` as a token separator
      instead of stripping it to nothing, so `stage_apply::run` no
      longer collapses to the unsearchable `stage_applyrun`.
    - `matchesSymbol` falls back to a file-path containment check when
      `qualifiedName` doesn't carry the module hierarchy (Rust
      file-level functions, Python free functions in a package): a
      `run` in `src/configurator/stage_apply.rs` now matches
      `stage_apply::run` because `stage_apply` appears as a path
      segment.
    - Qualified lookups that don't match the qualifier no longer fall
      through to fuzzy text matches — `stage_apply::nonexistent_fn`
      returns `null` instead of resolving to an unrelated `rollback`
      in the same file.

[0.8.0]: https://github.com/colbymchenry/codegraph/releases/tag/v0.8.0
[0.7.10]: https://github.com/colbymchenry/codegraph/releases/tag/v0.7.10

## [0.7.8] - 2026-05-17

### Fixed
- **opencode**: install actually wires up the MCP server now. v0.7.7 wrote
  `~/.config/opencode/opencode.json`, but opencode reads `opencode.jsonc` by
  default — so the `codegraph` entry never showed up in any opencode session.
  The installer now prefers an existing `.jsonc`, falls back to `.json` when
  only that exists, and creates `.jsonc` for greenfield installs. **Re-run
  `codegraph install --target=opencode` after upgrading** so the entry lands
  in the file opencode actually reads.

### Added
- **opencode**: installer now writes `AGENTS.md` (global
  `~/.config/opencode/AGENTS.md`, local `./AGENTS.md`) with the same
  codegraph usage guidance the other agents already received. Without it,
  opencode's model would call native `Grep` instead of the `codegraph_*`
  tools it could see in its MCP list.
- User comments and formatting in `opencode.jsonc` survive install /
  re-install / uninstall round-trips — surgical edits via `jsonc-parser`
  rather than full-file rewrites.

[0.7.8]: https://github.com/colbymchenry/codegraph/releases/tag/v0.7.8

## [0.7.7] - 2026-05-17

### Added
- **Multi-agent installer** (closes [#137](https://github.com/colbymchenry/codegraph/issues/137)).
  `codegraph install` now opens with a multi-select prompt for **Claude Code**,
  **Cursor**, **Codex CLI**, and **opencode** — detected agents are pre-checked.
  Each writes its native MCP config + instructions file (e.g. `~/.cursor/mcp.json`
  + `.cursor/rules/codegraph.mdc`, `~/.codex/config.toml` + `~/.codex/AGENTS.md`,
  `~/.config/opencode/opencode.json`). The runtime MCP server was already
  agent-agnostic; this brings the installer to parity.
- Non-interactive install flags for scripting / CI:
  `--target=<csv|auto|all|none>`, `--location=<global|local>`, `--yes`,
  `--no-permissions`, `--print-config <id>`.
- `codegraph init` now auto-wires project-local agent surfaces for any agent
  configured globally. In practice: Cursor's `.cursor/rules/codegraph.mdc`
  is dropped on `init` so a single global `codegraph install` works in every
  project you open — no per-project re-install needed.

### Fixed
- **Cursor**: globally-installed codegraph reported "not initialized" in every
  workspace because Cursor launches MCP-server subprocesses with the wrong
  working directory and doesn't pass `rootUri` in the MCP initialize call.
  We now inject `--path` into Cursor's MCP args — absolute path for local
  installs, `${workspaceFolder}` for global installs.

### Changed
- Agent-instructions template is now agent-agnostic. The previous template was
  inherited from the Claude-only era and prescribed "spawn an Explore agent" —
  a Claude Code-specific concept that confused Cursor's and Codex's agents and
  caused them to fall back to native grep even with codegraph available. The
  new template adds explicit "trust codegraph results, don't re-verify with
  grep" guidance and a clear tool-by-question matrix. Applies to
  `~/.claude/CLAUDE.md`, `.cursor/rules/codegraph.mdc`, and `~/.codex/AGENTS.md`.
- `codegraph install` prompt order: agent picker is now step 1, before the
  PATH-install and location prompts.
- Disambiguated "global" wording in install prompts ("Install codegraph CLI on
  your PATH?" vs "Apply agent configs to all your projects, or just this one?")
  — both used to say "Global" and read as duplicates.

### Internal
- New `AgentTarget` interface in `src/installer/targets/` — adding a 5th agent
  (Continue, Zed, Windsurf, …) is a new file + one entry in `registry.ts`.
- Hand-rolled TOML serializer for Codex (`src/installer/targets/toml.ts`) — no
  new dependency, scoped to the `[mcp_servers.codegraph]` table only, sibling
  tables and `[[array_of_tables]]` preserved verbatim.
- +47 parameterized contract tests across the 4 targets — install idempotency,
  sibling preservation, uninstall reverses install, byte-equal re-runs return
  `unchanged`, partial-state recovery for Codex.

Based on substantive draft by [@andreinknv](https://github.com/andreinknv)
([fork commit `c5165e4`](https://github.com/andreinknv/codegraph/commit/c5165e4)).
Thank you.

[0.7.7]: https://github.com/colbymchenry/codegraph/releases/tag/v0.7.7

## [0.7.6] - 2026-05-13

### Fixed
- `codegraph` CLI failing with `zsh: permission denied: codegraph` after a fresh
  global install. The published 0.7.5 tarball shipped `dist/bin/codegraph.js`
  without the executable bit, so the shell refused to run it through the npm
  symlink. The build now `chmod +x`'s the binary before packing.

  Already on 0.7.5? Either upgrade to 0.7.6, or unblock yourself in place:
  ```bash
  chmod +x "$(npm root -g)/@colbymchenry/codegraph/dist/bin/codegraph.js"
  ```

[0.7.6]: https://github.com/colbymchenry/codegraph/releases/tag/v0.7.6
[0.9.6]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.6
[0.9.7]: https://github.com/colbymchenry/codegraph/releases/tag/v0.9.7