Repository navigation
Conversation
KAI_GRAPH=off (graph.Disabled, kai-engine#128) already turns off the harness graph summary, the graph tools and kai_grep's symbol route. The review command builds one more graph-derived block itself — the planner's injected context — so it now checks the same switch. With it the whole review runs without the semantic graph, which is what a graph-on vs graph-off comparison needs. Requires the kai-engine release that carries graph.Disabled. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jschatz1
force-pushed
the
feat/symbol-call-edges
branch
from
October 29, 2026 13:03
3fd3001 to
71b3d17
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
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.
Why
KAI_GRAPH=off(graph.Disabled, kaicontext/kai-engine#128) turns off the harness graph summary, the graph tools and kai_grep's symbol route. The review command builds one more graph-derived block itself — the planner's turn-0 injected context — so it now checks the same switch. With it a whole review runs without the semantic graph, which is what a graph-on vs graph-off comparison needs. Default behaviour is unchanged.The experimental callers-of-changed-code block (
KAI_REVIEW_BLAST_CONTEXT) that was in this PR has been removed: on the benchmark it showed no gain over graph-on (F1 −0.6 Opus, +1.1 Sonnet, −4.9 GPT, n=45).Status — ready once the engine release lands
Compiles only against the kai-engine release carrying #128 (
graph.Disabled). After kai-core#9 → kai-engine#128 → kai-corev0.1.3tag, the cascade's adopt-engine bump lands on main; rebase this on it and CI goes green.Tests
go vet ./cmd/kai+go test ./...green against local engine/core.🤖 Generated with Claude Code