Kotlin

What .kt / .kts add beyond Install, CLI specs, and Graph schema: heuristic vs scip-java, the env flags, and the ids those pages do not spell out. Toolchain fit: cg doctor -h. Why a file stayed heuristic: cg coverage.

Modes

--min-confidence resolved (or exact) hides the heuristic call edges. Gradle build/ (including KSP / kapt), .gradle, and IDE folders are skipped. tree-sitter-kotlin 1.1.0 rewrites some sources before parse (same length, so lines and names stay). A file that still errors is split into members (files_reparsed_by_member, members_dropped_by_reparse); dropped members are in cg coverage --details.

Exact mode

A scip-java index replaces name-based call edges. Ids stay the syntax layer's, so queries and cg link match both modes. Running scip-java runs the project's Gradle / Maven build, so it is opt-in.

cg reads the version the build declares, tries the matching release first, then the next if the compiler plugin does not load. Index stats record kotlin_version, indexer, and failed attempts. cg doctor <project> names the release that fits. install.sh --with kotlin installs the supported pair (Windows: cg doctor).

Java in that index becomes java nodes with the Java plugin's ids (method:pkg.Foo.bar, not method:pkg.Foo::bar), including fields, and exact Kotlin ↔ Java and Java → Java calls, including AppKt.build(), a @file:JvmName facade, Foo.Companion.x(), @JvmStatic, and getX / isX / setX on a Kotlin property. The two layers do not create a second node for the same Java symbol. Without the index, .java files are indexed by the Java plugin (heuristic), and Kotlin → Java calls resolve through imports and the same package; Java → Kotlin calls resolve FooKt.bar(), Foo.Companion.x(), @JvmStatic, and getX / setX / isX (Java interop). A --scip file with Java documents is consumed by the Java plugin. Go and other languages still use the generic importer. Spring facts for both languages are extracted by the shared JVM module cg_code_graph/plugins/jvm/spring.py (Java). Stats exact_vs_heuristic is precision (heuristic call edges the compiler confirms) and recall (compiler edges the heuristic layer had found). Property read / write edges stay and are left out of that pair; a property read is not a call in the SCIP index.

Query specs

Class.method and Class::method follow query targets. Kotlin-only shapes:

A custom get / set, by lazy, or other delegate is a method: / function: node (kotlin_kind: property). Reads and writes are CALLS (property: read / write / read_write); calls inside the accessor carry accessor. impact prints a callable reference as (ref: callback) (REFERENCES_FN, how: callback, both modes), an accessor body as (get) / (set) / (lazy) / (delegate), and a stored-property initializer as (in a property). Two to five methods of one name are candidate edges (binding: "candidate"): flagged by cg tests / impact, left out of platform divergence. A library-typed receiver (Headers.build { }, client: HttpClient) is not bound by name.

Framework facts

cg index examples/bookstore-django  --db /tmp/dj.db
cg index examples/bookstore-android --db /tmp/android.db
cg link --backend /tmp/dj.db --frontend /tmp/android.db --db /tmp/android-link.db
cg path "page:kotlin:checkout/{bookId}" "table:catalog_order" --db /tmp/android-link.db