dynamic_context

Create an empty node graph. Use only when a new graph is needed that belongs to nothing yet — an agent version already has one, reached with get_draft.

Read a conversation graph whole: its root node, every node (name, instructions, position, the tools it offers) and every edge with its condition. An agent's draft names its graph's id.

Delete a graph with all its nodes and edges, permanently. Use only on a graph that belongs to nothing — never an agent version's own graph.

Connect two nodes of a conversation graph. Use when adding one new path the agent may take between two existing nodes. condition is the label the model chooses by. Refused (422, reasons) when another edge leaving the same node already carries it (compared trimmed, case-insensitively): two branches with one label is a branch the model can never take, and it is never stored.

This is the agent graph. A flow's steps are connected with add_flow_edge.

Remove an edge from a conversation graph. Use when a path between two nodes should no longer exist.

This is the agent graph; for a flow, use delete_flow_edge.

Add a node to a conversation graph. Use when adding one new situation to a graph that already exists; use replace_draft_graph to write a whole designed graph at once instead.

A node is one place the conversation can be: its own context for the model, and its own tools. name is what a person calls the node in the editor and in history — set it when a graph has more than a few nodes; the model never reads it, so it is not where behaviour goes. instructions are. Refused (422, reasons) when tool_ids would offer a tool name the agent already has, globally or on another node.

Delete a node and every edge touching it, permanently. Use when removing one situation from the graph.

Change a node's name, instructions, position, or tools. Use when editing one existing node; only the fields sent change. name is what a person calls the node; the model never reads it, and null clears it. instructions is for what the agent should say and how it should behave in this situation — never a business fact, which is a record in a collection, and never a procedure, which is a flow. tool_ids is where a tool reaches the agent in one situation: instance ids from create_tool (a flow registered as a tool included), the query_/get_/write_ tools a collection created, or a published custom tool's tool_id. For a tool the agent should have in every node, or one that runs before or after the conversation, use edit_draft. Refused (422, reasons) when tool_ids would offer a tool name the agent already has. This edits the draft's graph; nothing takes traffic until publish_version.

Set the node a conversation starts at. Use when designating or changing which node is the graph's entry point.

A graph without a root cannot be published.