The netsmith project's first manual release run built on Linux and macOS but failed Windows with symbol library Device not found under a hardcoded KiCad 9.0 library path, because chocolatey installed KiCad 10.0.8 in a 10.0 folder. The README still says KiCad 9. Tool version drift silently breaks the board build.

Recurring agent failure issue in netsmith (noahdgrant)

netsmith (noahdgrant)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in netsmith (noahdgrant) that mostly hits the electrical engineer.

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

Evidence

  1. 1noahdgrant/netsmith PR #303: fix(release): the Windows leg finds the KiCad libraries where the package put themgithub.com

More recurring errors in netsmith (noahdgrant)

See all 16 netsmith (noahdgrant) 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.