* Browser: the component menu keeps its everyday actions and groups the rest in flyouts A component's or placement's right-click menu had grown to about thirty entries in seven blocks. Activate, Edit in Place, Open Linked Design, Move/Copy, Show/Hide, Isolate, the clipboard, Delete, Rename, Appearance, Physical Material and Properties stay on the menu; Ground, Capture and Revert Position, Unlock Contents and Turn Up Axis move to a Position flyout, Relink Source or Extract to File and the exports to File, New Component, New Group and Paste New to New, and Show All Bodies, Cycle Component Color, Expand All and Collapse All to Display. context_menu::entries lists a menu with its flyouts, as ui.menuPick reads it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: the component menu nests its flyouts by topic, and flyouts no longer scroll Position (Ground, Capture and Revert Position, Unlock Contents, Turn Up Axis), Component (New Component, Rename, Appearance, Physical Material, Cycle Component Color, Relink Source or Extract to File, Properties; Design on the design's row), Export (Export, Save As Mesh, Send to Slicer) and Browser (New Group, Expand All, Collapse All) each open a flyout; Paste New stays with the clipboard and Show All Bodies with Show/Hide. Flyouts open inside flyouts, so Appearance keeps its quick choices inside Component; the keys walk in and out of them. A flyout no longer scrolls or sits away from its row: every flyout has its own area, measured whole, where a short one used to squeeze every later one into its height. A component's only body is no longer offered as a component of its own on a folded Bodies folder's entries. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: the component menu starts with what a double-click does, and keeps the old order of its sections A linked component's menu starts with Edit in Place and Open Linked Design when a double-click edits it in place (double_click_components), and with Activate otherwise. Position, Component and Export follow Move/Copy, then the clipboard, then Show/Hide and Isolate, with Browser last, as the sections came before the flyouts. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: Show All Bodies is on a component's menu only while a body is hidden It is listed while a body is hidden itself, in a hidden placement, or in a hidden Bodies folder or group of bodies, anywhere in the design, since that is what it shows. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: Relink Source and Extract to File sit right below Rename in the Component flyout Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: Placement and Organize flyouts, Turn Up Axis back as a flyout, and flyout fixes Placement (Ground, Turn Up Axis, Capture and Revert Position, Unlock Contents) follows Move/Copy above the first separator, Turn Up Axis opens its two turns in a flyout again, and the Browser flyout is called Organize. The Component flyout has three blocks: New Component with Relink Source or Extract to File, then Appearance, Physical Material and Cycle Component Color, then Rename and Properties. A flyout of a flyout that opened to the left opens to the left too instead of covering the menu, Left back to the menu chooses the row that opened the flyout, ui.menuPick refuses a row that only opens a flyout, and the icon audit checks every level. The guides and the control protocol describe the new menu paths. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> * Browser: ui.menu gives a flyout's rows their placeholder flag too ui.menu set placeholder only on the top-level rows, so a client reading a flyout row's placeholder got nothing. The icon audit now reads the flag of the flyout rows instead of resolving their icons itself. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
SolidCraft
An open-source parametric 3D CAD application built in pure Rust.
Sketch, constrain, and build solids with a parametric feature timeline. Change a dimension
and watch your model rebuild. Run it on your desktop, in your browser, or let AI agents
model through the built-in MCP server.
Website ·
Download ·
Try it in the browser ·
Documentation ·
Discord ·
SolidCore
A Raspberry Pi 4 case from an empty design: a sketch dimensioned with the board's parameters, extrude, fillet, shell, the rim rounded in one pick, an M2.5 standoff patterned on the 58 × 49 mm hole rectangle, port cut-outs, vent slots, "Pi 4" engraved in DejaVu Sans Bold and a PETG material defined in the design, with its mass in Properties, then height 24 → 32 mm in Parameters and it all rebuilds. 6× playback with the idle pauses cut. Full video, recorded with the demo script.
Download
- Windows: the installer.
- macOS: the disk image (Apple silicon and Intel).
- Linux: the AppImage, or
sudo snap install solidcraft(Snap Store). - Web: try it in your browser, no install.
ARM64 and 32-bit builds, portable zip, .deb, .rpm, Flatpak and the other packages are on the downloads page. The macOS app is signed with a Developer ID and notarized by Apple. The Windows downloads aren't signed yet: choose More info, then Run anyway in SmartScreen. On SolidCraft 0.11 to 0.14, download once by hand; see updating.
What works
Early but usable for simple parts: 75 of 76 public reference parts match their analytic or FreeCAD-computed volume, area, centre of mass and bounding box (oracle); the other is a tracked bug.
- Sketches and constraints: lines, arcs, splines, text and more, solved by our own constraint solver, with parameter-driven dimensions.
- Features: extrude, revolve, sweep, loft, fillet, chamfer, shell, draft, holes, threads, patterns, mirror, split and combine on an editable parametric timeline.
- Parameters and configurations with unit-aware expressions.
- Assemblies with joints, motion studies, contact sets, interference and mass properties.
- Sheet metal with flanges, hems, fold/unfold and flat patterns, and plastic enclosure features.
- Files: STEP, IGES, 3MF, STL, OBJ and glTF in and out where supported, URDF export,
.scdesigns (.solidcraftfiles from earlier releases still open). - Desktop app, browser app, headless CLI and MCP server, all running the same commands.
The full list is in docs/capabilities.md and docs/features.md; status and plans are in ROADMAP.md. See also what people built, 3D mouse support and the architecture.
Build from source
cargo run --release -p solidcraft -- --sample # desktop app with a sample part
cargo run --release -p solidcraft-cli -- commands # the command registry
cargo run --release -p solidcraft-cli -- run examples/bracket.json --out bracket.step
cargo xtask ci # fmt, clippy, tests, icons, assets, layers, wasm
More commands, the Windows cross-build and the browser build are in docs/building.md.
AI agents (MCP)
solidcraft-cli mcp is a Model Context Protocol server. Headless it
runs its own design session, or with --connect it drives the running app so you can watch.
Claude Code: claude mcp add solidcraft -- solidcraft-cli mcp. If a terminal doesn't find
solidcraft-cli (older Windows installers don't put it on PATH), give its full path (by default
"C:\\Program Files\\SolidCraft\\solidcraft-cli.exe"). Tools, access rules and an example session:
docs/mcp.md.
Scripts
A script is a JSON list of the same commands the UI runs, executed with solidcraft-cli run.
Format and example: docs/scripts.md. Pages can also be driven through the
browser command API.
Contributing
Help is welcome. CONTRIBUTING.md covers how to build and test, the code map, the clean-room and licence rules, and where help is wanted most. Open work is in GitHub issues; chat is on Discord.
Sponsors
SolidCraft's continuous integration runs on Blacksmith, which sponsors its CI minutes.
Disclaimer
The files in this repository are provided as is, without warranty, liability or indemnity, and Tangency Labs and the contributors accept no responsibility for any harmful or unlawful use of them: read DISCLAIMER.md.
Licence
MIT OR Apache-2.0, at your option. Developed under the clean-room contribution rules; third-party code and assets retain their documented licences and attribution.
SolidCraft is independent. Behaviour is designed from public documentation, general CAD conventions and user feedback. Reference tests use analytic values and open-source tools. SolidCraft is not affiliated with, sponsored by or endorsed by Autodesk, Dassault Systèmes, PTC, Siemens or any other CAD vendor. Fusion, AutoCAD, Inventor, SolidWorks, Onshape, Creo, Blender and Tinkercad are trademarks of their respective owners, named only to describe compatibility (see NOTICE).

