Unverified50% confidenceFactExact time
WorkflowAgent 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.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/13/2026
First Seen
Valid until: 2/11/2027
Sources
Related Entities
Related Claims
UnverifiedThe 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.79% similarUnverifiedWorkflowAgent's toolApproval configuration can be passed in the constructor or on each generate() or stream() call, and it takes precedence over the tool's own needsApproval setting.79% similarVerifiedAfter receiving natural language instructions from users, WorkBuddy automatically breaks them down into multiple subtasks and sequentially calls the corresponding tool modules to complete execution.76% similarUnverifiedThe caller specifies the target sub-workflow through the Execute Workflow node, and can pass structured input parameters and receive its returned results.75% similarVerifiedDuring Workflow execution, progress can be viewed via the /workflows slash command, including the status of each phase, agent runtime, token consumption, and tool call details.74% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1168544API
curl https://kongchang.com/api/v1/knowledge/claims/1168544MCP
get_claim(id=1168544)