The partcad remote sandbox rewrote file paths on the command line but not in the request on stdin, so readers looked for files that did not exist in the container. IGES parts failed with OpenCASCADE could not read plate.igs, and STEP assembly imports broke the same way. The sandbox lost every file path passed in the request, so STEP, IGES and URDF imports failed in upload mode.

Recurring agent failure issue in partcad (partcad)

partcad (partcad)MCADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in partcad (partcad) that mostly hits the mechanical designer.

Failure pattern: validation / failure

Analyst note

From the Grok pain-radar digests, Nov 9-10 2026 (Nov 9 7:41 AM ET through Nov 10 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-10: issue/PR read; title and state confirmed.

What it costs a team

Modeled annual cost

$30,000

For a team of 5

Prototype delay

3 days

Modeled schedule slip per occurrence

Time lost

240 min

Per engineer per month, about 1 incidents

How the cost is modeled

240 min/month × 5 engineers × 12 months = 240 hours × $125/hour = $30,000

A modeled estimate with medium confidence. Swap in your own team size and loaded rate to size it for your team.

Engineering tools that address it

No engineering tool profile lists this error yet. Browse tools that connect to partcad (partcad).

Evidence

  1. 1partcad/partcad PR #944: Carry a wrapper's request paths to a sandbox that is sent filesgithub.com

More recurring errors in partcad (partcad)

See all 10 partcad (partcad) errors

Sourced from public community reports. Costs and delays are modeled estimates, not measurements. Know a better source or a fix? Tell us at hello@productflo.io.