Every standalone via triggers a 'missing courtyard' warning and the KiCad export writes an empty reference that native DRC flags. Their workaround is their own packaging adapter that hides it. Both opened in September, active again tonight.
Recurring agent failure issue in core (tscircuit)
What engineers report
A recurring agent failure problem in core (tscircuit) that mostly hits the electrical engineer.
Failure pattern: validation / 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 core (tscircuit).
Evidence
More recurring errors in core (tscircuit)
- A generated schematic dropped the VBAT net label on paired power pins: U1.BAT1 and BAT2 and C17.2 all connect to net.VBAT in source, but the schematic wired the two chip pins together with no VBAT label so they ended up separate from C17 (confirmed with KiCad's native netlist).ECAD · impact 74
- A JSON save and import round trip flips an antenna feed pad from masked to unmasked, adding a solder-mask opening that should not exist, and a wider 60-pad test lost ten coverage flags and thirty mask margins.ECAD · impact 74
- A standard usb_c connector resolved to a different footprint over time because the JLC parts engine ranks by stock and ignores the manufacturer part number, with the snapshot flipping from a through-hole part to JLC C2765186 with no code change, and setting manufacturerPartNumber did not pin it.ECAD · impact 74
- A trace written to U1.pin2 quietly attached to an internal pad port instead, with no error, so the net never reached the copper.ECAD · impact 74
- Companion core PR in the rotation stack, confirmed red on main with expected 0, received undefined for the rotation value.ECAD · impact 74
- Core PR in the rotation stack: core leaves schematic_component.rotation unset even after the visual MOSFET rotation fix shipped, and this PR emits the angle; both PRs are blocked on publish order.ECAD · impact 74
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.