Unverified50% confidenceFactExact time
In the Agent context, a trace refers to recording a task execution as a hierarchical call tree, where the root node is the user goal, child nodes are each model call and tool call, and each node carries input, output, latency, and token consumption.
1
Sources
50%
Confidence
Long-term
Relevance
10/26/2026
First Seen
Sources
Related Entities
Related Claims
VerifiedThe Agent's workflow can be summarized as: receive user instructions → decompose complex tasks into multiple sub-steps → sequentially invoke corresponding tools to execute → aggregate results and output.76% similarVerifiedIn agent scenarios, a complete agent task should be treated as a single Trace, with each LLM call, tool call, and memory retrieval being a Span.76% similarUnverifiedThe Agents API has three levels: a Session is a persistent task container, a Turn is a single advancement or iteration within it, and Items are the messages, commands, tool results, and final outputs generated during an advancement.75% similarUnverifiedThe Task Token mechanism issues a token containing the task description and permission scope from a trusted coordination layer when an Agent task starts, and each resource call must carry the token and verify whether it falls within the scope of intent73% similarUnverifiedAgent系统中的Checkpoint实现思路与Git版本控制中的分支和回退、数据库中的事务回滚在本质上是同构的，操作对象从代码或数据变成了Agent的推理状态72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1098211API
curl https://kongchang.com/api/v1/knowledge/claims/1098211MCP
get_claim(id=1098211)