Unlogged/spontaneous python indentation changes yielding errors

Support Bug Reports
1

Describe the Bug

Without any manual, human change, or logged change from cursors chat/agent, indents for individual lines or large sections of code will change with no apparent cause. Of course this is absolutely crippling for python development.

Steps to Reproduce

Write large class heavy python programs, often but not always triggered by loads or prompt rollbacks in agent/chat.

Expected Behavior

My code should not just be changing on its own.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Latest standard releases, existed on previous update as well at least, instructions to find this info formatted as desired are unclear/out of date.

Additional Information

This is just an absolutely ridiculous issue, absolutely absurd that code is just changing with no clearly identifiable source. I’ve seen it documented twice, over the course of the last two months, both marked resolved with no actual resolution.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

2

Hi @Henry_Pharris and thank you for the bug report.

You can check your Cursor version:

  1. Through the application menu:
  • Open Cursor
  • Click on “Help” in the menu bar
  • Select “About Cursor”
  • The version number will be displayed in the dialog box
  1. Through the command line:
  • Open Command Prompt or PowerShell
  • Run: cursor --version
  • The version will be displayed in the terminal
3

This is happening to me a LOT too… I have tried everything … I have no autoformatters installed, Git whitepace removal disabled… nothing stops it from happening. It’s always the same lines that get messed up, and it happens after Cursor edits my large file. Something is causing some weird aggressive diff or reformat across the whole file causing dozens of lines to get incorrectly indented. Yet when I correct them, it just happens again after cursor does anything (not to those lines). It’s extremely annoying and it’s caused by cursor .. I have ruled out all other causes at this point.