You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
java: impact says 'the change is local' about an entry point it just said the outside world calls #1467
impact on an entry point says "Changing it changes what the outside world can call", then ends with next: nothing resolved depends on it, so the change is local. The next: line is word for word the one given for a method nothing calls at all. Measured on 0.1.3 at 0df257c; CLI impact and the MCP axiomcode_impact tool print the same text.
$ axiomcode impact WidgetController.count
entry point: WidgetController.count is a http entry point -- a framework invokes it, so no client call site reaches it. Changing it changes what the outside world can call.
next: nothing resolved depends on it, so the change is local -- read src/main/java/app/WidgetController.java:6 and edit there
$ axiomcode impact Widgets.spare # control: not an entry point, same next:
next: nothing resolved depends on it, so the change is local -- read src/main/java/app/Widgets.java:4 and edit there
A main method and a servlet doPost registered in web.xml give the same pair of lines.
Root cause
plugins/axiomcode/skills/axiomcode/scripts/axiomcode-impact: the entry-point line is printed at 1769 from ep_by_reason, but next: (lines 2133-2142) builds places from the contract and the direct dependents only, so an entry point with no in-graph caller takes the "change is local" branch at lines 2141-2142.
Expected: when the target is an entry point, next: says its callers are outside the graph and does not call the change local.
Activity
swapnilpaliwal-sd commentedon Sep 28, 2026
Fixed by #1615, merged into 0.1.4.
impact, path: never "local" or "independent" past the evidence the an…