use-rhino

Use the run_python tool, which executes CPython 3.13 inside Rhino on the UI thread with __rhino_doc__ as the slot's document. Import the document, records, canvas, and assembly modules to add geometry, manage layers, and read results back as records.

Run uv run --script scripts/file3dm.py with a file or folder path. It uses openNURBS via the rhino3dm package to print one JSON line per file with layers, materials, object counts, bounding boxes, and validity logs, with no Rhino process involved.

Yes, one Rhino process holds every slot, and each call must pass its slot identified by the recorded pid and port pair. Scripts never activate another session's document, restore views and selections in finally blocks, and avoid modal-raising calls that hold the UI thread.

Call g2_start first, then use g2_search_components and g2_apply_graph to place components and wires, and solve with an empty g2_apply_graph. The canvas module reads output values, assigns inputs, places script components, and bakes results onto layers.

Deadlocks occur when scripts wait on other UI-thread work such as a Grasshopper 2 solve or Task.Wait, or when a macro contains _Pause waiting for a viewport pick. Modal dialogs also hold the UI thread for every session and must be avoided.

The convert and export functions use typed writers for suffixes including STEP, IGES, SAT, Parasolid, OBJ, and glTF. Conversions run in headless documents on the UI thread under a 5 minute limit, and .glb preserves physically based materials for Blender.