The CLI posted a 27-hour rotary CNC program that the app Save gate would have refused, and said nothing: the refusal lives in the app store and engrave.ts posts files directly and never consults it, so a headless run and the app disagree about what may leave the building, silently. A second bug in the same receipt has an oversize warning claiming Generate refuses a part before building the toolpath when it did not.

Recurring agent failure issue in CaseMaker (SlyWombat)

CaseMaker (SlyWombat)MCADAgent failureMedium confidence

What engineers report

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

Failure pattern: agent / silent failure

Analyst note

From the Grok pain-radar digests, Nov 8-9 2026 (Nov 8 8:41 AM ET through Nov 9 6:41 AM ET digests plus the Haitch editions). Verified live 2026-11-09: 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 CaseMaker (SlyWombat).

Evidence

  1. 1SlyWombat/CaseMaker Issue #1084: cli: `casemaker cut` posts a rotary .nc silently past the app's Save gate, and goal-object-oversize fires falsely on an axis-centred rotary goal (claiming a refusal it does not make)github.com

More recurring errors in CaseMaker (SlyWombat)

See all 3 CaseMaker (SlyWombat) 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.