Unverified50% confidenceFactExact time
The semantics of WorkflowAgent's prepareStep return value have been aligned: the returned instructions (or the deprecated system) replace the current step's instructions and propagate onward, providerOptions are merged with the agent options, and headers override the call's own headers.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/13/2026
First Seen
Valid until: 2/11/2027
Sources
Related Entities
Related Claims
UnverifiedWorkflowAgent supports experimental_refineToolInput in the constructor and per call, and the refined tool input is used for tool execution, step results, callbacks, and the next model call.79% similarUnverifiedThe solution designs two return paths: process progress (public text, tool status, etc. organized by the adapter into unified events) and completion notification (results are collected and a notification is sent when the task ends, and the main process decides whether to resume or deliver).71% similarUnverifiedThe caller specifies the target sub-workflow through the Execute Workflow node, and can pass structured input parameters and receive its returned results.70% similarUnverifiedTool call traces contain input parameters, return results, reasoning paths, business rule trigger conditions, and exception handling logic, which combined are nearly equivalent to executable business process documentation.69% similarUnverifiedTool calling refers to the mechanism by which an Agent requests the execution of an external function through a structured message and has the result returned; the returned content enters the conversation history as a message with role: 'tool' and from then on permanently occupies the context.68% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1168542API
curl https://kongchang.com/api/v1/knowledge/claims/1168542MCP
get_claim(id=1168542)