Product / Collaborate
A team of agents that operates the tools, not a chat window beside them.
Describe the outcome the way you'd brief a group of engineers. The agents split the job across your workspace — sketching, features, measurement, simulation, CAM — using the same tools you use by hand, in the document you have open. What they leave behind is a human-editable feature history: fully defined sketches, named relations, and the critical dimensions you specified.
Describe the outcome
Name the part, the critical dimensions, and what must not change.
You don't need to know tool names or write JSON. A brief that states intent and constraints gets better work out of the agents than a list of button clicks, for exactly the same reason it does with colleagues.
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.
Each agent's activity appears in the copilot feed, and their geometry lands in the same feature tree you use manually — sketches fully defined, relations named. Nothing lands in a parallel, opaque model.
- Inspect geometryRead the open model rather than guessing at it.
- Create and edit featuresOrdinary, fully defined sketches and features in your 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.
Provider connection
Your provider. Your account. Your bill.
In Settings → Providers, sign in with a supported provider account or paste your own API key. The prompt, the project context needed for that turn, and tool results go to the provider you picked — nowhere else.
Your provider's plan, API prices, usage limits, and privacy terms apply. Chudware doesn't sell tokens or resell model capacity.
Treat every provider credential as a secret. Enter it only in Provider settings—never in chat, a prompt, or a project note.
| Aspect | Provider account | API key |
|---|---|---|
| Setup | Authorize a supported account from Provider settings | Enter a key issued by the provider in Provider settings |
| Usage | Uses that account's plan and limits | Uses that provider project's API billing and limits |
| Billing | Your provider bills the account owner | Your provider bills the API account owner |
| Prompts | Sent only to the provider you select for the turn | Sent only to the provider you select for the turn |
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.