MetaForge (FidelOdok) errors

20 recurring problems engineers report in MetaForge (FidelOdok), ranked by impact.

#16 by errors trackedECADVerificationMCADFirmware

Recurring MetaForge (FidelOdok) errors, by impact

  1. 1Agent requirements matrix passed 16 of 16 requirements even though every requirement's value, limit and margin were null, and after a fix 7 of 14 stayed 'no_data' while the numbers sat in other tools' results.ECAD · Agent failure · 1 report82
  2. 2An autonomous agent released a desk lamp as Ready for production and it could not be assembled: the board mounting holes missed the cover, the hinge washers did not fit their gaps, the diffuser was larger than its seat, and the USB-C socket sat 8 mm inside the board edge. The board DRC also failed, and five of the seven G-code files were sliced from older CAD revisions.Verification · Agent failure · 1 report82
  3. 3A clean routed board with 0 unrouted and 0 DRC could not be exported because the guardrail tagged Gerber, BOM and pick-and-place exports DESTRUCTIVE, refusing every fab file export to a remote agent.ECAD · Agent failure · 1 report74
  4. 4A gate got reviewed only once, at the moment it opened. On their sandbox, a Chair run's DFM gate opened while the approval policy was off. The policy was switched to auto at 17:27 and the gate still never got a review, so the run sat waiting for a person. The fix re-checks open, unreviewed gates when the policy changes and from a supervisor loop. Approval state and run state lived in two places and nothing reconciled them.MCAD · Agent failure · 1 report74
  5. 5A headless agent built a desk lamp's 7 validated CAD parts, board and firmware but could not release it because it never found the release and baseline tools and no manifest tied the files together.Firmware · Agent failure · 1 report74
  6. 6A non-M3 mounting hole got a bare footprint with no library id, so the Specctra export wrote a nameless component and the routed session import failed, leaving the board with only plane fanout and 96 unconnected items.ECAD · Agent failure · 1 report74
  7. 7An agent-run BOM of 7 sourced parts passed every gate while resistors and capacitors had no manufacturer part number, because kicad.export_bom returned only KiCad's default columns, and a fab house can only place what it can buy.ECAD · Agent failure · 1 report74
  8. 8In an agent end-to-end run, all 16 requirements were stored with the placeholder expression True and counted as evaluated passes, though requirements like drc_error_count equals 0 and board_length_mm at most 40 were never compared to anything even though the routed board already held those numbers.ECAD · Agent failure · 1 report74
  9. 9KiCad export reported F.Paste and B.Paste as written, but the fab package contained no paste or stencil layers at all.ECAD · Agent failure · 1 report74
  10. 10On their sandbox, a chair design run from the built-in mech_v1 template had every agent write held as untrusted, so a person had to approve dozens of tool calls on top of the real gates. The fix trusts a run whose recorded flow hash matches the shipped template, while tailored or patched flows stay held.MCAD · Agent failure · 1 report74
  11. 11The agent left out source_node_ids, so the schematic had no link to the BOM and the board STEP none to the routed layout, and the STEP was mislabeled as a FreeCAD export.ECAD · Agent failure · 1 report74
  12. 12The agent run drew a Bosch BMI270 with KiCad's BMI160 symbol and nothing recorded it, because ERC and netlist match both pass on the stand-in's own pins.ECAD · Agent failure · 1 report74
  13. 13The CAD adapter logged Assembly created over an empty folder, and a board STEP could not be validated: every twin.build_assembly failed without being reported because the gateway made a root-owned output folder the uid 1000 adapter could not write to, and CadQuery Assembly.save ignores the OCCT STEP writer return status. A second bug sent a 2.6 MB board STEP as about 3.5 MB of base64, hit aiohttp 1 MiB limit, and the agent saw Invalid JSON.MCAD · Agent failure · 1 report74
  14. 14The desk lamp release passed DFA with zero findings while the USB-C port faced the wrong wall and the BOM was empty: the receptacle faced +Y with its slot in the +X wall, the slot was too small for a plug to seat, no hinge pin or screw existed, and the BOM had 0 items. The fix reads the connector mating axis from the footprint and board placement and checks it against the enclosure slot normal.MCAD · Agent failure · 1 report74
  15. 15In a hardware digital twin dashboard, opening a schematic after its board showed a broken image whose alt text named the PCB's SVG under the schematic node, because a cached node re-rendered without remounting and combined the new node's id with the old node's file, and it only showed on a cache hit.ECAD · Agent failure · 1 report66
  16. 16MetaForge's published package shipped a forge command that could not start, and four files disagreed about the version so /health reported 0.1.0 while releases had reached 0.3.x. CI missed both because it ran from a full checkout.ECAD · Agent failure · 1 report66
  17. 17run_erc returned passed=true on every real report because it read the wrong JSON level; a faulted drone flight controller showed 2 errors in kicad-cli and 0 in the tool.ECAD · Agent failure · 1 report66
  18. 18Running photo-to-3D end to end, the STEP part-colour rule was applied to every format, so the GLB that the Tripo tool told the model to commit was always refused. Tripo also started returning HTTP 400 when no model was named. A rule written for one format blocked the agent's handoff between two tools.MCAD · Agent failure · 1 report66
  19. 19Wrapping Zoo for CAD conversion in an MCP server, the expected headline feature, text to CAD, was not there: the REST endpoint returns 404, and the copilot now returns KCL source, not STEP. Agent builders are chasing vendor APIs that move under them.MCAD · Agent failure · 1 report66
  20. 20The same hardware digital twin returned 404 for this node has no prior version on its parameter and geometry diff routes, while the versions route answered the same question with an empty 200, so every node selection logged two fake errors.ECAD · Agent failure · 1 report58

How it fails

  1. Agent failure20

Engineering tools that address these errors

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