On a 40 x 40 mm board, edakit route all reported both GND pours ok, then no-copper on both, and said the bridge refuses every further fill until EasyEDA restarts. Saving, restarting and rerunning gave the same result twice, even though GND pads sit under both pours. What worked was manual: create pours, save, restart EasyEDA, then call the rebuild once per pour id in a set order, then put the tooling holes back.
Recurring agent failure issue in edakit (tgd1975)
What engineers report
A recurring agent failure problem in edakit (tgd1975) that mostly hits the electrical engineer.
Failure pattern: agent / 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 edakit (tgd1975).
Evidence
More recurring errors in edakit (tgd1975)
- A bought USB-C breakout wired to the made board by cable is not in the design graph because every board in the graph has to be one edakit makes. Its missing CC resistors were found by another session after the order list was written, not by a check; with the breakout modelled, the check flags CC1 and CC2 as not connected.MCAD · impact 74
- A gate run fails the hole check for U1 and D23 to D30. All nine have lead sizes in the parts database, keyed by manufacturer part number because they are bought at Berrybase, not LCSC, and edakit check, edakit sim and even pcb apply find those entries, but the fab release hole check looks parts up by LCSC code only, so it never sees them. The origin has no workaround.ECAD · impact 74
- A project's stitching script adds vias and a pour to the PCB but can only run unregistered, by hand, and its step order lives as a note in CLAUDE.md rather than in the tool.ECAD · impact 74
- After one rebuild the easyeda-mcp-pro bridge cannot verify, so it refuses every later rebuild until EasyEDA restarts, while edakit carried on with empty pours.ECAD · impact 74
- An LED whose parts entry lacked a role the simulation reads was silently left out of the netlist, so earlier checks never saw it.ECAD · impact 74
- Checked live on EasyEDA Pro 3.2.209 with easyeda-mcp-pro 1.8.0. The server's net listing takes parts and flags from every loaded page but wires from the focused page only, then joins them by coordinates. With the layout_tree page closed, pin U4.11 drops off the V_LED net again. The author first blamed EasyEDA, traced it to the bridge, and drafted an upstream issue and PR without posting them. The workaround stays in place. An agent reading this board gets a different netlist depending on which tab a human left open.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.