kicad-cli-extended (Hybirdss) errors

9 recurring problems engineers report in kicad-cli-extended (Hybirdss), ranked by impact.

#49 by errors trackedECAD

Recurring kicad-cli-extended (Hybirdss) errors, by impact

  1. 1After an autoroute added 9 DRC errors, fab package still produced a JLC Gerber zip marked complete true with exit 0, unless the caller remembered a --fail-on-drc flag. The author's own words: an agent that gates on complete would send a shorted board to the fab.ECAD · Agent failure · 1 report74
  2. 2On KiCad's pic_programmer demo, pcb place near put a VCC pad on another net's track and exited 0, so DRC later found shorts and solder mask bridges. The update step also reported unrouted connections using pre-placement coordinates about 100 mm off, and a worker crash reported placed.skipped with exit 0.ECAD · Agent failure · 1 report74
  3. 3An agent branches on the tool's exit code and stdout, and several paths sent it the wrong way: a rolled-back save printed a success-shaped result, two processes editing one project failed as an internal error, and a refusal before any save said commit_state unknown, which the skill tells the agent means repair storage.ECAD · Agent failure · 1 report66
  4. 4An autoroute threw away 651 seconds of routing. Grid auto refinement failed on its last step after 651 s on pic_programmer, exit 2, nothing saved. The DRC before/after gate also counted unrouted connections as new errors, so a partial route was refused and nothing saved. Follow-up to PR #10 from the 7:41 sweep.ECAD · Agent failure · 1 report66
  5. 5On a non-English machine every ERC fix hint came back null because the wrapper parsed kicad-cli's translated messages. On KiCad 10.0.8 a valid STEP export got reported as a crash because the check looked for an English log line that build no longer prints.ECAD · Agent failure · 1 report66
  6. 6The autoroute and placement gates compare KiCad DRC before and after an edit by item UUID. KiCad 5 boards store no UUIDs for pads or some tracks, so every load invents new ones and every old finding looked new. A routing edit far from the problem exited with DRC has 1 new error(s) and a placement was refused. Two earlier fixes matched findings by position, then by position and description, and reviewers broke both.ECAD · Agent failure · 1 report66
  7. 7The autoroute reported routed 21, failed 0 while DRC went from 0 to 9 errors, because the router used fixed 0.6/0.3 mm vias against the board's 0.9/0.5 mm minimums and ignored copper text. Sizes now come from the board rules, and any new DRC error exits 3 without saving.ECAD · Agent failure · 1 report66
  8. 8The first write to a KiCad 9 board upgrades it to KiCad 10 format, so the ECO compare flagged format-only changes as unexpected. A correct one-part change failed with 72 entries while a track-by-track check found none of 815 tracks and vias moved.ECAD · Agent failure · 1 report66
  9. 9With every track ripped, grid auto kept refining down to 0.05 mm and then failed with Grid too large after 651 s, exit 2, nothing saved. Separately the new before/after DRC gate refused partly routed nets because leftover unrouted connections name the new tracks.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure9

Sourced from public community reports. Costs and delays on individual entries are modeled estimates, not measurements.