Coharyn Impact — Documentation
Getting started with Coharyn Impact.
Install the plugin, run your first assessment in about a minute, and learn how to read what it tells you — confidence labels, the risk breakdown and Change Packs.
Install
Your first assessment in 60 seconds
Open a Java or Spring project
Let the IDE finish indexing — assessments need the semantic index and start automatically once the IDE is in smart mode.
Assess a symbol (Free)
Right-click a Java method or class in the editor and choose Assess Impact. Coharyn shows its direct relationships — callers, implementations, Spring components, persistence, config and tests — each with evidence.
Assess your working tree (Pro)
Make an uncommitted change, then run Assess Current Changes. Coharyn maps your Git diff to semantic symbol changes and rebuilds the full blast radius with a risk score.
Open the evidence
Click any finding to navigate to its source location and see the mechanism that discovered it, with its confidence label.
Reading the results
Every relationship carries a source location, the mechanism that discovered it, and a confidence label. Where evidence is missing, the assessment says “Not established from available evidence” rather than guessing.
Resolved by the IDE's semantic index — the strongest evidence available.
Established structurally, e.g. a declared implementation or explicit annotation attribute.
Found by convention (e.g. test naming). Always flagged so you can weigh it.
The risk breakdown
Pro assessments include a deterministic 0–100 Change Impact Risk score. Open “Why this score?” to see each contributing factor and its weight. The score is an evidence-weighted indicator of where scrutiny is warranted — not a probability of failure.
Risk: HIGH — 62/100 +20 1 public contract change +15 1 method signature change +12 6 direct callers/references detected +10 1 affected path with no discovered related test
Change Pack export
Free vs Pro
Free — free forever
- Assess Selected Symbol
- Direct relationships (depth 1)
- Navigation and full evidence view
Pro — 7-day free trial
- Assess Current Changes
- Full impact depth (depth 3, bounded fan-out)
- Change Pack export
Trials and purchases run through your JetBrains account. See pricing for details.
Troubleshooting highlights
The action is greyed out or missing
Assess Impact appears in the editor context menu of Java files only. Assess Current Changes requires an open project — it reads the IDE change list.
“Coharyn is waiting for indexing to finish…”
Assessments need the IDE's semantic indexes. Wait for indexing to complete (progress bar in the status bar) — the assessment starts automatically once the IDE is in smart mode.
Assessment seems incomplete
Free analyses direct relationships (depth 1); Pro analyses depth 3. A “bounded” note in the header means a cap was hit (≤400 nodes / ≤120 references per symbol) — the true radius may be larger, and this is stated, never hidden. Kotlin and other non-Java files are listed under “not semantically analysed”.
No tests found, but tests exist
Coharyn discovers tests by resolved references first, then by naming conventions (FooTest, FooTests, TestFoo, FooIT — flagged HEURISTIC). Tests that reach your code only through reflection or DI wiring without any source reference cannot be confirmed — an evidence limit, reported honestly.
Performance
Assessments run in background tasks and are cancellable from the progress bar. On a very large project, cancel and assess a smaller changelist or a selected symbol. The plugin never blocks the UI thread — an IDE freeze involving Coharyn is a P0 bug; report it with idea.log.
License not recognised
Check the license is active in your JetBrains account (it can take a minute to sync). Help → Register… shows license state per plugin. Coharyn re-checks at most every 10 minutes — restart the IDE to force it. Offline, JetBrains' standard offline grace window applies.
Logs: Help → Show Log in Finder/Explorer. Coharyn log lines are tagged AssessmentService/Coharyn and never contain your source code. Still stuck? Head to support.