STEP import in cad-rust-app dropped part names and colours, and the project needed a colour.py script to put the Onshape colours back. Bodies came in grey and named Part N. Colours were written as linear RGB, so #ff8000 showed up as #ffbc00 in other programs and on re-import. The fix reads names and colours through OCCT's XCAF reader and never overwrites names set by hand.

Recurring agent failure issue in cad-rust-app (JonasMerrell)

cad-rust-app (JonasMerrell)MCADAgent failureMedium confidence

What engineers report

A recurring agent failure problem in cad-rust-app (JonasMerrell) that mostly hits the mechanical designer.

Failure pattern: validation / failure

Analyst note

From the Grok pain-radar digests, Nov 10-11 2026 (Nov 10 8:41 AM ET through Nov 11 7:41 AM ET digests plus the Haitch editions). Verified live 2026-11-11: 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 cad-rust-app (JonasMerrell).

Evidence

  1. 1JonasMerrell/cad-rust-app PR #128: Keep STEP part names and colours on importgithub.com

More recurring errors in cad-rust-app (JonasMerrell)

See all 4 cad-rust-app (JonasMerrell) 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.