Unverified50% confidenceFactExact time
After the fix f3d7a10, WorkflowAgent passes the runtimeContext returned by prepareStep to that step's approval policy, instead of continuing to use the context from when the call started.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/17/2026
First Seen
Valid until: 2/15/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.75% similarUnverifiedWorkflowAgent 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.69% similarUnverifiedAfter Plan mode is enabled, WorkBuddy first plans the task and waits for user confirmation before executing.67% similarUnverifiedAfter the fix 7655f47, WorkflowAgent passes the tool metadata, dynamic flag, and title of server-side tool definitions to the toolApproval policy, both for newly initiated tool calls and for calls re-approved from message history replay.66% similarVerifiedAsynchronous tool-calling mode allows the application layer to submit time-consuming operations for background execution while letting the model continue processing other subtasks that have no dependencies.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1181308API
curl https://kongchang.com/api/v1/knowledge/claims/1181308MCP
get_claim(id=1181308)