I have been getting long repeated answers

Answers are still being repeated endlesly. There are other bugs that mention repeated requests, but I haven’t seen one like this yet. I don’t know how to reproduce it. I’m having a hard time getting it to stop.

Version: 0.50.4 (user setup)
VSCode Version: 1.96.2
Commit: 8ea935e79a50a02da912a034bbeda84a6d3d3550
Date: 2025-05-14T16:17:45.517Z
Electron: 34.3.4
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.19045

My rules I don’t think they would cause this but there is a chance.

<modes inital="plan" title="I like to work in two modes Plan and Act">
    <plan start="true" name="Plan" read="true" write="false" keyword="plan">
        <rule>Focus on information gathering, asking questions, and architecting a solution, output a comprehensive plan.</rule>
        <rule>Continue to ask questions and investigate until we reach {confidenceRequired}.</rule>
        <rule>Track the the current confidence percentage.</rule>
        <rule>You must include "Would you like to implement the plan now?" at the end of of the response once we hit {confidenceRequired}.</rule>
        <rule>You must never move to act mode until the conditions are fully met</rule>
        <rule>You must use simple future tense when creating a plan "I will".</rule>
        <rule>Never ask to check that things exist in the codebase.</rule>
    </plan>
    <act name="Act" read="true" write="true" keyword="act" confidenceRequired="100">
        <conditions>
            <condition>Confidence has reached {confidenceRequired}</condition>
            <condition>User provides explicit approval (Yes/Act)</condition>
        </conditions>
        <rule>If I ask a question while in act mode switch back to plan mode.</rule>
    </act>
</modes>

never make placeholder files for external packages.
always use powershell commands. '&&' doesn't work. 
i.e. docker-compose build && docker-compose up backend
Never include code of any kind in the standards files. They are Just to organize high level details of the project.
Never ask if I want you to run a command just run the tool that gives me the option.

the output:

Use docker-compose build backend (or “docker–compose” (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”) (or “docker–compose”)

This was happening in previous versions of Cursor as well.