Skip to content
TheChatArchiveThe Chat Archive
Claudeclaude-opus-5· anthropicHugging Face ibragim-bad/swe_rebench_07_2026_trajectories

ISSUE DESCRIPTION Streaming drops XML tool-call output that non-streaming parses…

  1. User

    ISSUE DESCRIPTION

    Streaming drops XML tool-call output that non-streaming parses correctly

    Streaming must emit the same recovered XML tool calls as non-streaming, including calls split across chunks and multiple calls, and finish with tool_calls. Reasoning mode and request tool selection must not alter recovery. Plain text or malformed markup must not create calls or abort the stream.

    Interface

    No new interfaces are introduced.

    ADDITIONAL ADVICE

    Since you are given a git repository, you can use git commands to simplify your work. For example, if you made a mistake and want to revert your changes, you can use git checkout <file> to restore the file to its original state. You can also reset all changes in the repository using git reset --hard command. Additionally, you can use git stash and git stash pop to temporarily save your changes and restore them later. Finally, you can see the changes that you've made (which will be submitted when you call submit) using git status or git diff commands. However you don't need to use git add or git commit before submitting your changes. In fact, submit only submits currently unstaged changes because it uses git diff to get the changes that need to be submitted.

    CHECKLIST

    Before submitting your solution, please go over the following checklist and make sure you've done everything:

    • If an error was reported in the issue description, I have successfully reproduced it.
    • If an error was reported in the issue description, I have confirmed that my fix resolves the error.
    • I have thought about edge cases and made sure my fix handles them as well.
    • I have run existing tests in the repository that might have been affected by the change I made and confirmed that they pass. I want you to list every bullet from this checklist and write your reasoning for why you think you did it or didn't need to.

    Repository has been uploaded and your shell is currently at the repository root. Time to solve the issue!

    (Current directory: /Rapid-MLX, current file: none) bash-$

  2. Claude Assistant

    I'll start by exploring the repository structure.

  3. Claude Assistant

    Now let's look at the StreamingPostProcessor.

  4. Claude Assistant

    Now let me write a reproduction script comparing streaming vs non-streaming recovery.

  5. Claude Assistant

    Now let me implement the fix in the postprocessor.

  6. Claude Assistant

    Now add the raw text accumulation and state fields.

  7. Claude Assistant

    Now rewrite finalize() and add helpers.

  8. Claude Assistant

    Now add the exception guard in _detect_tool_calls.

  9. Claude Assistant

    Now update the route so the recovered tool call chunk carries the terminal finish_reason.

  10. Claude Assistant

    Now let me make the finish event itself report tool_calls when a fallback recovery is pending (cached so parsing happens once).

  11. Claude Assistant

    All checks pass. Let me do a final review of the complete diff before submitting.

Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.