For most people, this bug first cropped up with the installation of extension version 2025.11, which first hit the streets two weeks ago, on November 13th.
Some people have reported success by rolling back to 2025.10, others have chosen to disable auto-save/auto-update. Feel free to do either, or just click “cancel” until the bug has been fixed.