Skip to main content
The core primitive is the single-prompt node, and an agent is a topology of them. The pieces are deliberately small: a node is a prompt and its tools, and control moves between nodes through handoffs you can see on the canvas.

​
The single-prompt node

A node is one model, one system prompt, and the tools that model can call. It has: A node can also carry any skills and knowledge bases you attach to it. See Knowledge and skills.

​
An agent is a topology

An agent is a set of nodes wired into a graph. One node is the entrypoint. Every conversation starts there. Each node steers the conversation with its own prompt and tools until it hands off to another node or ends the call. Here triage is the entrypoint. Each labeled edge (continue_to_lookup, continue_to_existing_patient_scheduling) is a handoff the model can call to move control.

​
Handoffs are tools

An edge is not a separate kind of thing. A handoff is a callable tool: an agent_swap tool on the source node whose target is named as a pair, target_key and target_version. Pinning the target version means a graph that is already serving traffic cannot be changed by a later draft edit. The tool’s description is the sentence the model reads to decide whether to take the path. Write it the way you would explain the transition to a teammate: “the caller is an existing patient and wants to schedule.” The consequence is the important part: if a handoff is not present as a tool on a node, the agent cannot take that path. The canvas and the runtime are the same data, so what you can see is exactly what the model can do.
Publishing an agent freezes the entrypoint and every node reachable from it through handoffs. A node with no handoff pointing at it is unreachable, and it is left out of the published version.

​
Nodes are addressed by key

Every node has a stable key, and handoffs, transcripts, and the engine all speak in keys, never row IDs. The reason is publishing. The draft is mutable; publishing copies the reachable draft into a new, immutable revision with new rows and new IDs. A row UUID is only valid until the next publish, but a key is stable for the life of the node. See Versions.

​
Building in the dashboard

The agent builder is fully editable. You can:
  • create and delete nodes, and edit prompts and model bindings
  • wire handoffs between nodes
  • attach deployed custom tools, skills, and knowledge bases
  • chat with the latest published version and inspect its traces

Tools

The four tool shapes a node can carry, and how they attach and run.

Versions

How the mutable draft becomes an immutable, numbered published version.