cli (tscircuit) errors

8 recurring problems engineers report in cli (tscircuit), ranked by impact.

#51 by errors trackedECAD

Recurring cli (tscircuit) errors, by impact

  1. 1Gerber via tenting landed in circuit-json-to-gerber 0.0.122 and the runframe updater picked it up, but the CLI stayed locked on 0.0.120, and a fresh install of the already-built CLI cannot replace its embedded converter, so published CLI ZIP exports still miss the bottom mask opening on a via that should be top-tented and bottom-exposed.ECAD · Agent failure · 1 report74
  2. 2Importing CAP1188 succeeds even when the datasheet metadata lookup returns 404, and the generated part names the exposed pad pin25 with no ground requirement although the datasheet says it is GND.ECAD · Agent failure · 1 report74
  3. 3The CLI bundles circuit-json-to-kicad 0.0.257, so KiCad ZIP exports drop an authored min_board_edge_clearance even though the fix shipped upstream, and KiCad falls back to its 0.50 mm default; on a real NEMA34 reduction, native KiCad 10.0.5 reports 4 copper-edge errors before and 0 after, with byte-identical PCB files. Second hour in a row the tscircuit CLI lock held back a published fix.ECAD · Agent failure · 1 report74
  4. 4The CLI's KiCad project export used a hardcoded stub .kicad_pro, so explicit board limits (min trace width, copper-to-edge clearance, via pad and hole sizes, netclass track width) did not make it into the KiCad file, even though a different code path in the same repo already exported them correctly.ECAD · Agent failure · 1 report74
  5. 5'tsci export -f glb' cannot load a component STEP model given by relative path (404), but 'tsci build --glbs' loads the same file. Export still writes a GLB, just without the model: 21 KB vs 63 KB. Anyone handing that GLB to an enclosure person gets a board missing parts and no error.ECAD · Agent failure · 1 report66
  6. 6`tsci check netlist` printed 'R1 (1kOhm undefined)' and listed resistor pins as anode and cathode, so the netlist people read to check a design was wrong about what is on the board.ECAD · Agent failure · 1 report66
  7. 7Plugin exports wrote 3D model paths with the ${KICAD_3RD_PARTY} variable, which left the models missing in KiCad 10.0.8. The fix switches to KiCad 9's versioned variable, which KiCad 10 still resolves, but it is another case of an ECAD to MCAD link breaking on a point release with no error.ECAD · Agent failure · 1 report66
  8. 8tsci check netlist and plain tsci check print "Errors: 1" for a floating must-connect pin and exit with code 0. tsci build on the same file exits 1. So any script or CI job, or any agent loop that reads the exit code, treats a broken netlist as clean.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure8

Engineering tools that address these errors

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