Block Wizard — build your own library
The blocks you keep rebuilding should be blocks. The wizard makes them, and they behave like the built-in ones.
What the wizard writes
A single .iblock file, in a plain text format with a version sentinel and four
sections:
- Header — identity, kind and ports;
- Icon — inline SVG, drawn in the library navigator like any other block;
- Description — the text shown on the hover card and in the configuration dialog, exactly as the built-in blocks carry theirs;
- Body — either recipe text, for a block built out of other blocks, or Python source.
Where they live
Your blocks appear under My Blocks in the library navigator, as their own grand-family beside the shipped ones, and the navigator rebuilds live as the library changes. Each tile carries Export, Delete and Show in Folder; the page carries Import. A block is one file, so sharing one with a colleague is sending them a file.
Stamping — why your projects stay portable
A definition is a stamp, not a new block type. Nothing registers itself into the block factory. When you place one, the wizard materializes ordinary blocks: a subsystem filled from the recipe body, or a Python block carrying the source.
The consequence matters. A project that used your library is a project made of standard blocks —
it opens, runs and exports on a machine that has never seen your .iblock file. Your
library is a convenience for authoring, never a dependency of the models you author with it.
See also: AI agents that edit the diagram · Your code in the loop
See it run on your own model.
Download the application from the customer portal, or read the documentation first — the manual, every block with its measured response, and the full command reference are public.