Skip to content

Pull in Roo tool calling fixes (PRs 10466 & 10519)#5179

Merged
lambertjosh merged 2 commits intomainfrom
cherrypick/approval-feedback-fix
Jan 19, 2026
Merged

Pull in Roo tool calling fixes (PRs 10466 & 10519)#5179
lambertjosh merged 2 commits intomainfrom
cherrypick/approval-feedback-fix

Conversation

@lambertjosh
Copy link
Contributor

@lambertjosh lambertjosh commented Jan 18, 2026

…466)

Cherry-picked from RooCodeInc/Roo-Code commit f2276be

Co-authored-by: Roo Code <[email protected]>
Co-authored-by: daniel-lxs <[email protected]>
@changeset-bot
Copy link

changeset-bot bot commented Jan 18, 2026

🦋 Changeset detected

Latest commit: aff6137

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package
Name Type
kilo-code Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

…icate (ROO-410)

When users approve tool execution with feedback text, the feedback was being
pushed as a separate tool_result before the actual tool executed and pushed
its own result. This created duplicate tool_results with the same tool_use_id,
violating the Anthropic API protocol (GitHub #10465).

Changes:
- Add approvalFeedback storage to hold feedback until tool completes
- Modify pushToolResult to merge stored feedback into the tool's actual result
- Update askApproval to store feedback instead of pushing as separate result
- Apply fix to both MCP tools and regular tools, native and XML protocols
- Update validateToolResultIds comments to clarify deduplication is now safety net

Cherry-picked from RooCodeInc/Roo-Code commit e4e67e27dc9c8b1e8f70a0bbd56d70ebcbf887f3 (#10519)
@lambertjosh lambertjosh force-pushed the cherrypick/approval-feedback-fix branch from 406367a to aff6137 Compare January 18, 2026 05:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants