Macadam Alpha · 13 October 2026
Macadam is a parametric CAD/CAM application for the browser and macOS, with its own Rust boundary-representation kernel. This catalogue describes the October 2026 production release. Feature presence does not mean every model or client interaction is supported.
Browse the catalogue
| Area | What it covers |
|---|---|
| Fusion, workspace, files and cloud | Fusion transfer, panels, navigation, rendering, file formats and encrypted storage |
| Modelling | Sketches, constraints, solids, surfaces, assemblies and sheet metal |
| Manufacturing | CAM operations, tooling, machine setups, simulation and G-code |
| GraphHopper and automation | Procedural graphs, plugins, JavaScript, model text and AI connections |
| Command reference | All 149 built-in command descriptors, with IDs, groups, shortcuts and declared platforms |
The headline: bring Fusion designs into Macadam
The Fusion exporter add-in and Macadam importer transfer complete design bundles, including supported editable sketches and history, parameters, assemblies, linked components and appearances. Open the exported folder or ZIP to continue modelling in Macadam.
Compatibility remains an alpha feature. Complex fillets, cuts, lofts, surface operations, some sketch data and broader sheet-metal history still have gaps. Unsupported operations retain source evidence and appear in Problems. External components use pinned exports; this is not live Fusion synchronization or a bidirectional history round trip.
Fusion details and limitations · Known import issues
At a glance
| Capability | Scope today |
|---|---|
| Parametric sketches | Drawing, constraints, dimensions, expressions, projection and patterns |
| Solid and surface modelling | Extrude, revolve, sweep, guided loft, booleans, blends, face edits and NURBS control grids; difficult geometry remains an active work area |
| Assemblies | Parts, instances, placement, seven joint types and interference checks |
| Sheet metal | Shared Rust bend-tree evaluation, flanges, hems, cutouts and flat patterns; authoring and import coverage are partial, with native command wiring still incomplete in this snapshot |
| CAM | 2D/2.5D operations, 3D roughing/finishing, tooling, simulation and controller posts; availability differs by client and setup |
| GraphHopper | Typed procedural graphs, reusable templates, data inputs and CAD command adapters; native editor parity remains in progress |
| Automation | JavaScript API, multiline scripts, model text, MCP and declarative plugins |
| Workspaces | Docking, multiple viewports, saved layouts, nested tabs and collapsible panel stacks |
| Storage | Local files, encrypted cloud organization and encrypted collaboration transport |
| Rendering | Materials, images, analysis views and camera modes; web shadow parity and native responsiveness remain open |
Reading support claims
- Implemented means the source contains the feature, not that every case has passed interactive validation.
- Partial identifies a restricted workflow or known capability gap.
- Platform debt identifies missing client wiring or interaction parity. A shared modelling command should run on both clients unless it requires a genuinely platform-specific service.
- Planned features are not counted as available.
The command reference records existing registry declarations, including current parity debt. It is not a guarantee that every menu, inspector or gesture behaves identically on Mac and web. No Windows/Linux desktop or iOS release is claimed here.