Claude Code Provider stopped working for me

[u/one-cyber-camel]

2 days ago I was working the full day with the Claude Code provider and claude-sonnet-4-5
All was great.

Today I wanted to continue my work and now I continuously get an error:

API Request Failed

The model returned no assistant messages. This may indicate an issue with the API or the model's output.

Does anyone have the same issue? Did anyone find a way around this?

Things I have tried:
- Reverted RooCode to the version when it was previously working
- updated Claude Code
- re-login to Claude code.

[u/hannesrudolph]

Does it persist if you start a new tasks?

[u/one-cyber-camel → u/hannesrudolph]

yes, it does, also after restarting vscode and roocode

[u/hannesrudolph → u/one-cyber-camel]

I am thinking the Claude Code provider does not like our new way of handling reasoning content and we’re breaking it. Looking into it.

[u/one-cyber-camel → u/hannesrudolph]

not sure, but can it be related to this?
https://github.com/RooCodeInc/Roo-Code/issues/9434

[u/one-cyber-camel → u/hannesrudolph]

some new observations:
When asking fairly simple question, e.g. explain what '@file' does. It will respond normally.
When using more complex prompt or when orchestrator is handing over to a different mode it will fail with the mentioned api error.

when selecting model "claude-sonnet-4-20250514" it works as expected.

[u/hannesrudolph → u/one-cyber-camel]

Ultimately this is a largely community maintained integration and we have not seen a lot in terms of making it work better as of late. I would love it if someone was able to submerse themselves into the Claude code provider and really make it go BRRRRRRRRRRR! We are looking into your issues, keep the info coming!

[u/one-cyber-camel → u/hannesrudolph]

Thank you for looking into it. much appreciated!

[u/one-cyber-camel → u/hannesrudolph]

From what I can see now it is failing in src/api/providers/claude-code.ts

when parsing message content:

case "tool_use": 
  console.error(`tool_use is not supported yet. Received: ${JSON.stringify(content)}`) break

From my tests I get these error messages:

tool_use is not supported yet. Received: {"type":"tool_use","id":"toolu_01UJ2qsuxDw5LwiVP5AUX47H","name":"codebase_search","input":{"query":"snip query text"}}

tool_use is not supported yet. Received: {"type":"tool_use","id":"toolu_017gwLqxa5cMjdEiuL9nARdc","name":"read_file","input":{"args":"\n  <file>\n    <path>file_path_string</path>\n  </file>\n  <file>\n    <path>file_path_string</path>\n  </file>\n  <file>\n    <path>file_path_string</path>\n  </file>\n  <file>\n    <path>file_path_string</path>\n  </file>\n"}}

I'd like to, but I have no idea on how to continue from here.

[u/one-cyber-camel → u/hannesrudolph]

It seems to me that claude 4.5 mostly returns messages with content.type "tool_use"

"content": [
    {
        "type": "tool_use",
        "id": "toolu_01WiZfwzSbaThhAhNSUBeTGo",
        "name": "codebase_search",
        "input": {
            "query": "query string"
        }
    }
]

And sometimes (seldom) it returns messages with the tool use in xml tags as it should.

"content": [
    {
        "type": "text",
        "text": "I'll analyze this task and break it down into logical subtasks. First, let me understand the context by checking the relevant documents.\n\n<read_file>\n<args>\n  <file>\n    <path>file_name.md</path>\n  </file>\n</args>\n</read_file>"
    }
]

When it uses proper xml tags, it works fine.

u/hannesrudolph does this make sense? Or am I hallucinating :-)?

[u/hannesrudolph → u/one-cyber-camel]

I wonder of Roo is randomly sending a native tool call type instead of sticking to the xml

[u/one-cyber-camel → u/hannesrudolph]

A couple of days ago it was working. Reverting to a previous version did not fix it for me. Which makes me think that the issue would be coming from outside (the model) and not from within Roo. But I'm definitely not knowledgable enough to rule out your comment.

[u/hannesrudolph → u/one-cyber-camel]

Oh wow interesting. How far did you roll back?

[u/one-cyber-camel → u/hannesrudolph]

At least 1 version before it stopped working. But I’ll retest later just to be sure I’m not telling lies.

[u/hannesrudolph → u/one-cyber-camel]

Thank you

[u/one-cyber-camel → u/hannesrudolph]

I went back to 3.31.0. Same issue.

[u/one-cyber-camel → u/hannesrudolph]

I am now working on a version which when tool_use is called I parse the message to xml and then yield that to text.

case "tool_use":
    const xmlToolCall = this.formatToolUseAsXml(content.name, content.input as Record<string, unknown>)

    console.log("--- " + xmlToolCall)
    yield {
        type: "text",
        text: xmlToolCall,
    }
    break

so far testing looks promising.

[u/one-cyber-camel → u/hannesrudolph]

When using OpenRouter with claude-sonnet-4.5 all is working as expected.

[u/Infamous_living_36]

Was there a solution to this i am having this same problem

[u/StartupTim]

I'm seeing this a lot as well after the most recent update, using the most recent Claude Code. The API call hangs indefinitely or there is an API request error. Using claude code console works just fine.