Unverified50% confidenceFactExact time
Before the fix b3588dc, WorkflowAgent would pass assistant replies containing tool calls to the toolApproval approval function, causing the approval logic to see pending, rejected, and invalid sibling calls and treat them as completed history messages.
1
Sources
50%
Confidence
Medium-term (~90 days)
Relevance
11/17/2026
First Seen
Valid until: 2/15/2027
Sources
Related Entities
Related Claims
UnverifiedIn WorkflowAgent, a tool call rejected by toolApproval receives an execution-denied tool result but does not pause the entire workflow.80% 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.78% similarUnverifiedCommit 57dadb5 decouples the creation of tool approval requests from the streaming logic, enabling WorkflowAgent.generate as well as stream without a writable stream to resume approved calls.71% similarUnverifiedIn the tool.call hook, when the agent attempts to edit code outside its worktree, the operation is paused and awaits human confirmation; if there is no response, execution is denied by default.69% similarUnverifiedThe 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.69% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1181306API
curl https://kongchang.com/api/v1/knowledge/claims/1181306MCP
get_claim(id=1181306)