cadsense (johari-dev) errors

3 recurring problems engineers report in cadsense (johari-dev), ranked by impact.

#158 by errors trackedMCAD

Recurring cadsense (johari-dev) errors, by impact

  1. 1An AI CAD review tool: syncing Onshape CAD took three steps, and the header Sync button failed silently when another chat in the same project was running, because the server refuses any sync during a run. Live Onshape downloads were not tested, since no key was available.MCAD · Agent failure · 1 report66
  2. 2Every cadsense sync after an Onshape edit cost 11 API calls, the same as a first import: reread the definition and BOM, re-export the full assembly as 3MF, refetch ambiguous parts. They now key on per-Part-Studio microversion IDs to carry unchanged parts forward.MCAD · Agent failure · 1 report66
  3. 3Onshape's 3MF export paints composite parts near-white (232,232,232) where the CAD shows 55,55,55, and the team had to fetch glTF instead.MCAD · Agent failure · 1 report66

How it fails

  1. Agent failure3

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