Memory for Onshape.
Your agent stops re-asking why a fillet is 2mm. Design decisions, tolerances, naming conventions, stored once, recalled across sessions.
Agents forget. Every single session.
CAD work is accumulated intent. An agent without persistent memory cannot participate in that accumulation.
The re-explanation loop
Every new session, the engineer re-explains the design context. "The M4 bolt is there because plate-A has 5mm clearance." The agent forgets overnight. The engineer types it again.
Lost design intent
Why is that fillet 2mm? Why is the wall 3.5mm thick? The decision made sense three weeks ago. Now it is tribal knowledge inside a single engineer's head - or worse, gone.
Vanishing naming conventions
plate-A-v3-FINAL-v2.stp. The agent invents new part names each session. Parametric references break. Assembly mates lose their targets. Two hours of rework for a name.
Built for the engineer who works with agents.
Two CAD platforms. Two agent runtimes. One shared problem: design context that evaporates between sessions.
Mechanical engineer
Works in cloud-based assemblies with parametric constraints and FeatureScript macros. Iterates fast across sessions.
Open-source contributor
Writes Python macros, builds reusable part libraries, and contributes to shared CAD workflows with strict naming discipline.
Four steps. No new workflow.
Works alongside any MCP client: Claude Desktop, Cursor, or any IDE with MCP support. Onshape and FreeCAD both covered.
Real conversation. Three days apart.
Same agent. Same project. 3 days later.
Session one: engineer explains the M4 choice. Session two: agent answers without being told again. That is the entire value proposition.
You control every memory. The agent does not.
The agent stores what you tell it, tagged with how it was created. You see the source on every recall. You can edit, delete, or audit anything in your terminal.
See everything stored
List every memory in a table: id, part-id, decision, who created it, date.
Fix or delete anything wrong
The agent has no veto. You always win.
Source-tagged on every recall
You see who said it. Trust accordingly.
Three ways to store memory. Pick the one that fits.
Memory persists across sessions and fades naturally if unused. Geometry never leaves your CAD tool.
Local
SQLite file on your machine. No accounts. Fully offline.
Trying it out. Offline work. Sensitive prototypes.
Hosted
Memory lives in our managed Supabase. We handle infrastructure, backups, and scaling.
Production use. You do not want to run infra.
Self-hosted
Your own Supabase project. You own the database, the keys, the data.
Compliance. Large teams. Sensitive enterprise data.
Works with any MCP-compatible runtime.
Drop into your existing IDE or agent runner. No new orchestration layer. The agent receives three tools and knows what to do with them.
The Model Context Protocol is open. If your agent speaks MCP, it speaks Vitalis.
Give your CAD agent a brain.
CAD support ships in the same vitaliscad package. One install, and your agent remembers every design decision across sessions.