Skip to main content
Every handle carries a data type. It’s how the editor knows which connections make sense — drag from an output and only compatible inputs accept the edge. A type describes what flows through a handle, not how many values; that’s a separate axis, covered in Lists & single values.

The types

The distinctions are semantic, not cosmetic. An image is not a video is not audio; model and collection preserve their specialized selectors rather than degrading to plain text; and a tool-list isn’t content at all—it’s agent wiring.

Compatibility

When you drag an edge, the editor checks the source type against the target type:
Type answers what flows. How many values flow — a single value versus a list — is a different axis entirely, covered in Lists & single values.

Handles, edges & connections

How handles emit and receive data, and the rules that govern edges.

Lists & single values

The other axis — how many values move through a connection.