DRC skipped clearance pairs inside one physical copper island, so a short between two intended nets could pass. The repro: merge two nets, route a bridge, then delete the joining schematic wire and accept the split while the copper stays. The schematic says two nets, the copper says one, and DRC said nothing. The fix adds an explicit short finding.

Recurring agent failure issue in pcbcraft (tangency-labs)

pcbcraft (tangency-labs)ECADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in pcbcraft (tangency-labs) that mostly hits the electrical engineer.

Failure pattern: validation / 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 pcbcraft (tangency-labs).

Evidence

  1. 1tangency-labs/pcbcraft PR #273: Report existing copper shorts between intended netsgithub.com

More recurring errors in pcbcraft (tangency-labs)

See all 8 pcbcraft (tangency-labs) 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.