The kct optimize-traces command reported 0 DRC errors and 0 rollbacks on a routed 4-layer mains board, but kicad-cli then found a missing connection on /AC_NEUTRAL that the report never listed, and kct creepage failed on a new pair, SCAP_POS_RTN to GND at 0.43 mm against 0.45 mm required. Without flags, the dry run also assumed a 2-layer 1 oz board while the file says 4-layer 2 oz. A silent open on a mains net is a safety defect.

Recurring agent failure issue in kicad-tools (rjwalters)

kicad-tools (rjwalters)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in kicad-tools (rjwalters) that mostly hits the electrical engineer.

Failure pattern: agent / silent failure

Analyst note

From the Grok pain-radar digests, Nov 9-10 2026 (Nov 9 7:41 AM ET through Nov 10 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-10: 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 kicad-tools (rjwalters).

Evidence

  1. 1rjwalters/kicad-tools Issue #8632: optimize-traces --drc-aware: reports 0 DRC errors but disconnects a mains net and introduces a creepage violation (caught by kicad-cli and kct creepage)github.com

More recurring errors in kicad-tools (rjwalters)

See all 62 kicad-tools (rjwalters) 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.