On a real KiCad 10.0.8 board, ERC and DRC passed and placement scored 100 out of 100, yet the overall quality gate still returned FAIL. It labelled a cosmetic advisory as an error, said 'Blocking issues remain', and pointed the agent at the warning as the first thing to fix. When a gate's verdict and its findings disagree, the agent chases the wrong fix.

Recurring agent failure issue in kicad-mcp-pro (oaslananka)

kicad-mcp-pro (oaslananka)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in kicad-mcp-pro (oaslananka) that mostly hits the electrical engineer.

Failure pattern: agent / false failure

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 kicad-mcp-pro (oaslananka).

Evidence

  1. 1oaslananka/kicad-mcp-pro PR #1688: fix: keep advisory-only project quality findings non-blockinggithub.com

More recurring errors in kicad-mcp-pro (oaslananka)

See all 15 kicad-mcp-pro (oaslananka) 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.