Arrange network layout
arrange_networkTidy existing node networks into a readable left-to-right data-flow layout, or apply exact coordinates atomically with stale-context checks and rollback. Never adds, deletes, or rewires nodes.
Instructions
Tidy an existing network into a readable left→right data-flow layout, or use layout_mode=explicit for one bounded, atomic exact-coordinate mutation with stale-context checks, readback and rollback. Annotation-aware automatic layout remains available, and omission of layout_mode preserves the legacy response. It never adds, deletes, or rewires nodes.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| path | Yes | COMP whose children to arrange, e.g. '/project1' or a container path. | |
| positions | No | Explicit mode only: normalized absolute child path to exact [x, y] coordinates. | |
| recursive | No | Also arrange the nodes inside nested COMPs (each network is tidied on its own). | |
| layout_mode | No | Keep automatic layout by default, or place exact coordinates atomically. | auto |
| target_source | No | Explicit mode only: use the supplied paths or compare them with active selection. | |
| include_docked | No | Move each node's docked DATs (e.g. GLSL *_pixel or callbacks DATs) with it by the same delta, like an interactive drag. Set false to reposition only the nodes themselves. | |
| idempotency_key | No | Explicit mode only: stable response-loss recovery key. | |
| annotation_aware | No | Treat each annotation and the operators it encloses as one layout unit. Uses structured bridge routes and never raw Python. | |
| annotation_padding | No | Padding in network-editor units when resize_annotations is enabled. | |
| resize_annotations | No | With annotation_aware, resize non-empty annotation bounds to the enclosed content plus annotation_padding. |