Skip to main content
A run can start other runs to delegate work. Each child has its own status, output, and events, while parent and root relationships connect the executions into a tree.

​
Parent and root

The parent is the run that started a child. The root is the first run in the execution tree. For a direct child, parent and root can be the same run; deeper descendants retain the same root but have different parents. For example, a support agent might delegate document analysis to another agent. That child could start additional work. The relationships let a client follow the original request through each execution.

​
Execution and conversation relationships

Parent and root IDs describe execution relationships. Conversation and message IDs connect an execution to chat content when those resources are present. A child run does not need to be displayed as a separate top-level message for its execution history to matter. Conversation-scoped responses can also identify the originating tool call. The selected response schema defines which links are available.

​
Results and permissions

A parent record does not replace its children’s results. When delegated work fails or remains incomplete, the relevant child’s status and events provide the details needed to investigate it. Access checks apply to each run. Knowing a parent ID does not grant access to all descendants. The run endpoints provide record and child-list operations. Observability explains how to correlate that history with logs and traces.