[feat] Claude Code Provider Native Tool Calling

[hannesrudolph]

Claude Code Provider Native Tool Calling

Implement Native Tool Calling in the Claude Code provider.

[roomote]

Oroocle   See task on Roo Cloud

Re-review completed for commit range 1e5ae81..095daee. No new issues in the latest commit; 1 previously-flagged item remains.

• Fix normalizeClaudeCodeModelId() to avoid using the in operator for model validation (it can match inherited keys like toString).
• When handling roocode://settings... docs links, pass values.section="providers" so the CTA lands on the right Settings section.
• Avoid in operator when validating Claude Code model IDs in the handler (use an own-property check for claudeCodeModels).
• Ensure Claude Code thinking_complete events persist the signature reliably for interleaved-thinking tool continuations (prefer emitting a thinking_complete stream chunk).
• Use own-property check for model validation in completePrompt() too (avoid in operator).
• Update filterNonAnthropicBlocks() docstring in streaming client to match current behavior (conversion removed).

Previous reviews

• 1e5ae81: Review #1
• 53733b8: Review #2
• b04932b: Review #3
• 0dad439: Review #4
• 0aa20c6: Review #5
• 5d9d57d: Review #6
• 65abdfc: Review #7
• 4094b84: Review #8
• 96d1ded: Review #9
• 043d3e8: Review #10
• 29b7c8f: Review #11

_{Mention @roomote in a comment to request specific changes to this pull request or fix all unresolved issues.}

[JonasPammer]

It seems like an implementation of #4799.
To get this accepted despite the fear of the grey area, I'd suggest creating a new provider and leaving the existing Claude Code alone.

This way - if it breaks and if Anthopic never creates a client ID marketplace to fix it, at least there's still Claude Code Wrapper.
Also, the Claude Code CLI situation with the new Opus may be resolved with future PRs.

I know what you are referring to with the current PR title (Kilo-Org/kilocode#3747 (comment)), but since it rewrites or adds the entire thing, it is very misleading

[hannesrudolph]

It seems like an implementation of #4799.

To get this accepted despite the fear of the grey area, I'd suggest creating a new provider and leaving the existing Claude Code alone.

This way - if it breaks and if Anthopic never creates a client ID marketplace to fix it, at least there's still Claude Code Wrapper.

Also, the Claude Code CLI situation with the new Opus may be resolved with future PRs.

I know what you are referring to with the current PR title (Kilo-Org/kilocode#3747 (comment)), but since it rewrites or adds the entire thing, it is very misleading

I hear you but existing implementation is broken and does not support native tool calling. We are migrating to native tool calling, and the current implementation cannot be salvaged in its present state. The alternative is to remove the integration entirely.

[JonasPammer]

oh sorry, i now just realize that you are a Roo Administrator and the person that has responded to the Discord Community Chats about this (for others reference, "Claude Code Opus 4.5 Unexpected API Response", claude code provider with existing claude code mcp ). That's awesome. I was just in fear that this will not get merged.

The alternative is to remove the integration entirely.

Please do not remove Claude Code (or i.e. Claude Max Subscription Usability, in this perspective) Integration, it's the only cost-reasoning way to use make heavy use of Claude.

Edit: Also found your sneak peek :) https://www.reddit.com/r/RooCode/comments/1pm40ro/roo_built_a_new_claude_code_integration_for_roo/

[hannesrudolph]

:) this is going to increase the stability and feature. No regression.

[JonasPammer]

Well, yes it works (except the prompt enhancer, but that's a me problem i think). Clever find out of the system prompt needed so the API reuqest doesnt get blocked with "you must be Claude Code" or similiar.

Guess I'll be using this branch this week at work to dive into benefits of Roo again, may report back if major things didn't work.

local tests (yes i know it's just selfaware-introspecting questions which aren't helpful or trustful, but yeah):

roo_task_dec-14-2025_8-49-01-pm.md
roo_task_dec-14-2025_8-56-27-pm xml.md
roo_task_dec-14-2025_8-58-58-pm question about thinking tokens low effort 16k.md
roo_task_dec-14-2025_8-58-20-pm question about thinking tokens high effort 64k.md
roo_task_dec-14-2025_8-57-18-pm question about thinking tokens none no thoughts.md

i guess high reasoning is the same as typing "ultrathink" in the claude code cli (though i thought it made it 32k) :).

one mention: when this get merged, it should also have code to convert old selection values (with dates) into one of the new 3 real options.

[hannesrudolph]

@JonasPammer Good catch on the prompt enhancement, likely applies to the context condensing as well! Will fix that now.

one mention: when this get merged, it should also have code to convert old selection values (with dates) into one of the new 3 real options.

Fixed!

[JonasPammer]

today at work with my max ^20 account it worked without errors too. i even implemented mcpm.sh to centralize my mcp's and roo could still access all flawlessly, cmd and sse mode.

Except for when I ask it to use/access Roo's Codebase Indexing, Unknown API Error ^10. Could also be a me problem or thus unrelated as not dove deeper (using free auggie mcp beta instead).

[hannesrudolph]

today at work with my max ^20 account it worked without errors too. i even implemented mcpm.sh to centralize my mcp's and roo could still access all flawlessly, cmd and sse mode.

Except for when I ask it to use/access Roo's Codebase Indexing, Unknown API Error ^10. Could also be a me problem or thus unrelated as not dove deeper (using free auggie mcp beta instead).

Someone else reported getting banned after using it all day.

The problem is not with the codebase indexing. If you want Roo to access it say "use the codebase_search tool with "red buttons" and it should search for buttons.

There is a fix coming for the MCP tool names. Should be merged.

What was the error detail when you hover over the api error and click the i icon?

[JonasPammer]

What was the error detail when you hover over the api error and click the i icon?

Oh, sorry, my fault - "Not authenticated with Claude Code. Please sign in using the Claude Code OAuth flow." (The Settings showed Sign In Button properly)
It's actually working x-x

Someone else reported getting banned after using it all day.

Still hope Roo doesn't completely ditch the CLI option. Or, at least, that if someone (even i'll try, even though never vscoded extension - good chance to get in) comes up with a proper rehaul/fix PR re-introducing that it would still be accepted.

[hannesrudolph]

What was the error detail when you hover over the api error and click the i icon?

Oh, sorry, my fault - "Not authenticated with Claude Code. Please sign in using the Claude Code OAuth flow." (The Settings showed Sign In Button properly)

It's actually working x-x

Someone else reported getting banned after using it all day.

Still hope Roo doesn't completely ditch the CLI option. Or, at least, that if someone (even i'll try, even though never vscoded extension - good chance to get in) comes up with a proper rehaul/fix PR re-introducing that it would still be accepted.

The CLI option is a subpar experience. It will not like be preserved as we are migrating to native tool calling.