check_join grades a hand join CLEAN when its end sits 40 nm off a pad anchor. KiCad then measures the net 0.12 mm longer, which is more than the default 0.1 mm intra-pair tolerance.

Recurring agent failure issue in KiCadRoutingTools (drandyhaas)

KiCadRoutingTools (drandyhaas)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in KiCadRoutingTools (drandyhaas) that mostly hits the electrical engineer.

Failure pattern: agent / false pass

Analyst note

From the Grok pain-radar digests, Nov 11-12 2026 (Nov 11 8:41 AM ET through Nov 12 5:41 AM ET digests plus the Haitch editions). Verified live 2026-11-12: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to KiCadRoutingTools (drandyhaas).

Evidence

  1. 1drandyhaas/KiCadRoutingTools Issue #1800: check_join accepts as CLEAN a join whose end is tens of nanometres off a same-net track end or pad anchor: the copper connects, but KiCad merges ends only when equal to the nanometre and measures the net 0.12 mm longergithub.com

More recurring errors in KiCadRoutingTools (drandyhaas)

See all 58 KiCadRoutingTools (drandyhaas) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.