Release Notes

Track changes that affect engineering workflows, interfaces and reproducibility. A documentation date records the documentation update; it does not establish a deployment or general-availability date for every described capability.

3 November 2026 — Documentation update

  • Established the central API/MCP service as the source of truth across Studio, REST, Python and MCP.

  • Replaced the proposed SDK resource interface with the implemented HTTP contracts and Python client.

  • Added generated references for 132 REST operations, 84 MCP tools and 18 conditional design operations.

  • Added implicit modelling guides for bodies, fields, lattices, parameters, constraints, physical regions and export fidelity.

  • Documented GD Structured Meshing and GD Hex-core Meshing, including named surfaces, intent controls, local/wake refinement, wall layers, CHT assemblies, quality review and export availability.

  • Expanded Fluxcore documentation for supported turbulence/laminar combinations, URANS/restart, DES/DDES discovery, CHT, rotation, outputs and convergence assessment.

  • Updated Studio guidance for Design/Simulate and shared agent-authoring drafts with revision review.

  • Added agent workflow guidance for discovery, units, ownership, idempotency, durable operations and result qualification.

Compatibility notes

The connected service determines actual availability. Mesh export requests need matching integration capabilities. The public solver-control catalogue governs accepted fields; newly developed controls are not supported until exposed there. Laminar flow currently uses the CHT contract. See migration.

August 2026 — Documentation preview

The initial Furo site introduced workflow guides, a preview API resource model, and NACA 0012 and plate-fin heat-sink studies. The preview API descriptions are superseded by the current API/MCP reference. Recorded validation results retain their original study conditions.

Future release entries

Each product release entry should state the release date and availability status, user-visible change, affected API/tool or workflow, migration action and relevant limitation. Numerical changes should identify whether comparisons with earlier runs need requalification. Do not use a documentation update to imply an unverified deployment.