Within one Value+Footprint group, Manufacturer, MPN, Farnell, Mouser and Digikey fields must agree. Differing values, almost always a copied symbol with half-updated fields, used to be comma-joined silently by kicad-cli. Their homemade release script now fails the build and names each ref. A team wrote its own release gate because the EDA export hides a BOM conflict a buyer would hit first.

Recurring agent failure issue in pcb_release (JitterCompany)

pcb_release (JitterCompany)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in pcb_release (JitterCompany) that mostly hits the electrical engineer.

Failure pattern: validation / 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 pcb_release (JitterCompany).

Evidence

  1. 1JitterCompany/pcb_release PR #3: BOM: fail on conflicting part fields within a groupgithub.com

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.