Saving a part in SolidCraft 0.14.0 changes who can open it. The new release reads older designs, but files it saves use format 25 and won't open in 0.13.x or earlier, according to its compatibility notes. If you share designs with someone still on an older release, agree on a version before editing. The October 16 release also adds FreeCAD and Rhino imports, so the compatibility change matters to people bringing existing parts into the application.
The Rust CAD project had 3,026 GitHub stars in MrKeyoor's October 16 candidate snapshot. It offers desktop and browser interfaces, with an MCP server for AI agents, under a choice of MIT or Apache-2.0 licenses. Its appeal is a design you can inspect and revise after an agent finishes working. What survives an import, a parameter change or a software upgrade determines how useful that promise is.
A model you can resize after the conversation
The project's recorded enclosure demonstration gives a concrete example: a Raspberry Pi case changes from 24 to 32 millimetres in height through a named parameter. Features that depend on that value rebuild. The website identifies the recording as an upstream demonstration played at nine times normal speed, so it should be read as an illustration of the workflow, without drawing conclusions about interactive performance from its pace.
In SolidCraft's feature guide, sketches acquire dimensions and geometric constraints before becoming solids. The resulting timeline keeps operations available for later edits, including suppressing or reordering features. For an enclosure, that offers a way to revisit a dimension instead of asking an assistant to generate the whole object again. The usefulness depends on the sequence rebuilding correctly when the dimension changes, which is a more demanding requirement than displaying the initial shape.
AI is optional, the project website says. A person can work in the editor without connecting an assistant, and agent-created designs remain available to open and edit there. That gives someone reviewing generated geometry a place to make corrections directly. It also means the application can be evaluated as a CAD editor before adding a model provider and an automation client to the setup.
An imported solid starts a different history
Version 0.14.0's release notes add .FCStd and .3dm imports through cadmpeg, alongside glTF imports as mesh bodies with colours and node structure. Those descriptions identify different representations. A file appearing in the viewport doesn't establish that all its contents can take the same subsequent modelling operations.
The project's format inventory makes the distinction explicit for STEP. Native SolidCraft files keep editable features, parameters and history. A STEP import becomes a base feature containing geometry, without restoring the originating CAD application's feature history. If you need to change the original sketch dimension that produced an imported part, the presence of its finished shape alone doesn't give you that sketch back.
The STEP importer documentation explains what you get instead. The file's boundary representation, or B-rep, describes connected surfaces and edges. SolidCraft retains the STEP text inside the design, so reopening doesn't require the original external file. Later operations can build on the imported bodies, such as adding a hole or rounding an edge. That's a new editable sequence layered onto the imported shape.
Assemblies bring another detail to check. The same import documentation says STEP product structure becomes nested components, with repeated parts represented as occurrences. Imported contents are rigid by default. Unlock Contents releases them for individual joints. A preserved component tree therefore doesn't mean a mechanism arrives ready to move. The reader also lists unsupported offset surfaces and pcurve-only edges, with unreadable elements producing warnings that can leave a body open.
Agent access includes inspection
SolidCraft's MCP documentation describes a headless design session and a bridge to the running desktop app. Both use the engine commands available to the interface and scripts. The tools include design inspection and measurement as well as parameter changes. That permits a useful feedback loop: make an edit, measure the result and revise it, with the person watching the desktop session when using the bridge.
The same MCP reference also describes a failure that automation authors should handle: if the app disappears during a request, the command may have run before the connection failed. It tells clients to inspect the design before repeating the change. Retrying blindly could apply a second operation to an already changed model. File access has separate boundaries, with design, recovery and scratch folders allowed under documented rules, and additional directories granted explicitly. An agent connection requires decisions about both modelling state and filesystem access.
The test report measures particular shapes
The project's reference-test report describes replaying a recipe and checking the result against expected values. Those checks include body count, volume and area, with centre of mass and bounding box comparisons. Where a reference mesh exists, the suite also measures surface distance. Each rebuilt part is exported to STEP, validated and read back. These are useful checks for whether a saved or exchanged model still describes the expected object.
Expected values come from hand-derived geometry or recipes built using FreeCAD's public Python API, according to the test methodology. FreeCAD runs as an external comparison tool rather than an application dependency. Some cases compare only volume and area where the kernels legitimately produce different shapes. That qualification matters: a passing scalar comparison establishes the property being checked, while leaving other aspects of the geometry outside that comparison. These are the maintainers' published results, not a completed MrKeyoor test of the release.
There is unfinished work directly related to editing. SolidCraft's roadmap describes persistent names for faces and edges, while listing remaining history work for sheet-metal, plastic and other features. Those identities help later operations find the geometry they depend on after earlier edits. A part that opens successfully still needs to survive the changes you intend to make. The roadmap's warning that command coverage doesn't establish workflow or geometric depth is a useful standard for evaluating the application.
Keep the original before trying the upgrade
For a trial, the getting-started guide offers a browser version as well as desktop installation. The browser uses WebGPU, with a WebGL2 option when that path is unavailable or misbehaves, and stores designs in the browser's private file storage. It needs HTTPS or localhost for that storage. Those details make exporting a copy of your work part of the evaluation, particularly when testing on a browser profile you might later clear.
Building from source is a separate commitment. In our SolidCraft review, dependency installation fetched 555 packages in 21 seconds, but the build and test commands each reached a 900-second timeout. The visible test log was still compiling and had no completed test summary. Those results leave our source verification unfinished. They don't establish how a downloaded release performs on a workstation.
The repository README calls the application early and suitable for simple parts, and says desktop downloads aren't signed yet. A sensible first experiment is a disposable copy of a part you understand: change a dimension, save it and check the reopened geometry against what you expected. Keep the original in its existing application and format while deciding whether the new editing workflow meets your needs.
The next development to watch is the geometry-kernel work referenced in the 0.14.0 release, which acknowledges slow fillets and boolean operations. For adoption, the useful evidence will be representative parts surviving edits and export at workable speeds. Until then, preserve a pre-upgrade copy before format 25 becomes the only editable version of a shared design.