Product
How CadPilot works
The assistant plans and operates, CATIA computes, the engineer decides. In between, CadPilot makes sure only checked steps reach CATIA and every change is measured.
A request in six steps
- Request. You describe the goal in plain language, ideally with dimensions and rules.
- Plan. The assistant breaks it down into tool calls and shows larger requests first.
- Check. CadPilot checks paths, file types, values and degenerate geometry before CATIA sees anything.
- Execution. CATIA computes in your visible session, on a working copy.
- Verification. CadPilot measures volume and features and reports a pad in the wrong direction as an error, not as a success.
- Decision. You review the result; every change of the session can be listed and undone.
Architecture
For non-developers: CadPilot is the controlled interface between AI and CAD. The detailed architecture is in the handbook.
AI assistant
An MCP-capable client with a model of your choice. It understands the request and calls tools – it does not compute geometry.
CadPilot
118 tools with a fixed schema, safe mode, data filter, rule checks, effect checks and session report. Runs locally as its own process.
CATIA V5
Your existing CATIA, driven through its documented COM automation. Dimensions, volumes and distances come from here.
No lock-in to an AI model
CadPilot is not the language model. It speaks the open Model Context Protocol; which assistant and which model sit behind it is your decision – cloud service, EU tenant or a local model on your own hardware.
| Client / model | Basis | Status |
|---|---|---|
| Open standard (MCP) | any MCP-capable client | architecture supports |
| GitHub Copilot (VS Code) | set-up, configuration and prompt collection documented | supported |
| Claude clients and other MCP clients | through the standard | architecture supports |
| Local models (e.g. via Ollama) | measurement script available, measurement with a real model pending | architecture supports |
No combination has been tested with a real CATIA yet – that follows with the validation. Until then nothing is listed here as “tested”.
Built-in safeguards
Working copies, not originals
Saving and export only go to a working folder, never over existing files.
Measure, don’t assume
A pocket into thin air or a pad in the wrong direction is reported as an error.
Undo
Parameter changes and new features can be undone; checkpoints for several steps.
No hanging on dialogs
If CATIA does not respond, CadPilot says so and sends no further commands.
Structured errors
Every error with a code and a safe next step instead of free text.
No administrator rights
Set-up in the user profile, no installation by IT needed.
All safeguards are verified offline against a simulator and real COM transport; confirmation in a real CATIA follows with the validation.