eda-agent (MOREmbedded) errors

8 recurring problems engineers report in eda-agent (MOREmbedded), ranked by impact.

#52 by errors trackedECAD

Recurring eda-agent (MOREmbedded) errors, by impact

  1. 1The Altium/EasyEDA agent's request ids put the session tag first and the trace logged only the first 8 characters, so perf joined on the session instead of the call. On a real workspace 1244 trace lines came back as 129 calls with nothing saying two thirds were gone.ECAD · Agent failure · 1 report74
  2. 2Altium MCP bridge: every status row showed the session id instead of the call id, so grepping the trace log returned every call; also notes the deployed Altium scripts on the machine are ahead of the branch (PCB.pas 5929 lines and others), so edits risk overwriting live code.ECAD · Agent failure · 1 report66
  3. 3Live checks in Altium 26.11 found that a refused or rejected obj_modify still read as success, and dry runs did not say what they would apply. The fix reports modified:false and stops the false 'Written to Altium.' message.ECAD · Agent failure · 1 report66
  4. 4Merging 23 upstream commits into an Altium agent fork, 655 to 758 tools; 18 conflicts were settled by 'the side that measured it won'. On impedance reference layers they had it backwards at first; upstream had rerun reads on a board with profiles and found the layers unreadable.ECAD · Agent failure · 1 report66
  5. 5The eda-agent doctor reported a critical FAIL of no process named x2.exe found while Altium Designer 26.11 was on screen and answering bridge commands, and the FAIL returned before the round-trip ping ran, so the contradicting signal never got a say.ECAD · Agent failure · 1 report66
  6. 6The proj_run_erc check stopped the Altium agent bridge on Altium Designer 26.11.1.5 with Undeclared identifier from two variables a commit added without declaring. A new lint for undeclared reads also found that FindPadNetByName was dropped by the 2026-10-10 merge while PCB_PlaceVia, PCB_PlaceTrack and PCB_RebindCopperToPadNets kept calling it, so the agent's ERC and its net-aware copper placement were broken for a month inside Altium's scripting layer.ECAD · Agent failure · 1 report66
  7. 7The tool meant to diagnose the Altium bridge reported Altium as down, with no version and no round trip, on a machine where it was running and answering. It trusted a process-table scan over the bridge; now it pings first and reports both.ECAD · Agent failure · 1 report66
  8. 8To tell which placements are stale, the agent first has to build its own offline copy of the whole Altium 365 workspace library as JSON and CSV, paging past the 10,000-row totalCount cap. GraphQL has no list of 3D models, so those get read from the Explorer panel through UI automation.ECAD · Agent failure · 1 report66

How it fails

  1. Agent failure8

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