Product / Collaborate
An assistant that operates the tools, not a chat window beside them.
Describe the engineering outcome the way you would brief another engineer. Chudware translates the request into normal sketches and features, works in the open document, and reports what changed. The result is an ordinary model you can inspect, edit, and revise.
Describe the outcome
Name the part, the critical dimensions, and what must not change.
You do not need to know internal tool names or write JSON. A brief that states intent and constraints produces better work than a list of button clicks, for exactly the same reason it does with a colleague.
Follow-ups work best when they ask for something concrete: measure the minimum wall thickness, show the right view, check interference with the housing. Measurements and renders reduce ambiguity — they do not certify a design.
Useful brief
“Add four M4 clearance holes on a 60 mm bolt circle, centered on the top face. Do not change the outer profile.”
Weak brief
“Open the sketch tool, click the circle button, then pattern it around a bit.”
The loop
Intent in, inspectable geometry out.
The copilot's activity appears in the copilot feed, and its geometry appears in the same feature tree you use manually. Nothing lands in a parallel, opaque model.
- Inspect geometryRead the open model rather than guessing at it.
- Create and edit featuresOrdinary sketches and features in the feature tree.
- Render viewsAlternate views to show what actually changed.
- Measure resultsConcrete numbers you can check against intent.
After a change
Four checks before a revision is worth saving.
Rotate and look
Inspect the highlighted feature in the 3D view. Geometry that reads correctly from one angle can be wrong from another.
Measure the critical dimensions
Use Evaluate on the dimensions that actually matter for fit, strength, or process.
Open the edited feature
Confirm its references. A feature attached to the wrong face is a problem that surfaces two revisions later.
Save a revision when it matches your intent
Not before. If the run went the wrong direction, stop it, explain the mismatch in plain language, and point at the last good feature or revision instead of stacking corrective edits on geometry you no longer trust.
How AI is provided
Managed capacity, or your own key.
During onboarding you choose how AI work is paid for and where it is sent. Managed work consumes Chudware credits. Bring-your-own-key work is sent directly through the provider you configured and does not consume Chudware credits.
A provider key you add belongs to your account and is entered in Chudware's AI setup screen. It is a secret: never paste it into a chat message or a project note.
| Aspect | Managed | Your key |
|---|---|---|
| Chosen | During onboarding | During onboarding |
| Requests go | Through Chudware-managed capacity | Directly to the provider you configured |
| Chudware credits | Consumed | Not consumed |
| Key location | Not applicable | Chudware's AI setup screen, on your own account |
Machine actions stay deliberate
The copilot may prepare CAM operations and output, but anything that affects a physical machine requires explicit operator review and control. Safety, tolerance, material, and manufacturing decisions remain yours.
Next
Try it against a model you can check.
Create a browser account, or build the first part by hand and then ask the copilot to revise it.