Generate commit message not working in 0.43.6

Hi, thanks for reporting an issue with Cursor.

Before you report this, we’d appreciate if you can search this forum to see if this issue has already been reported.

If you have done so, pleae check this box.
on

Describe the Bug

Updated Cursor today to Version: 0.43.6, not sure what was the exact version prior to it but it had the Generate commit message and it was working - now nothing happens when I press the button.

Steps to Reproduce

Press Generate commit message and see that nothing happens

Expected Behaviour

Generates commit message.

Operating System

Windows 10/11
MacOS
Linux

Current Cursor Version (Menu → Abount Cursor → Copy)

Version: 0.43.6

Additional Infomation

No, I don’t have more info and the requirement that this field must be 20 chars or longer is ridiculous.

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, I just checked and it works for me. Have you tried restarting Cursor?

Yes. Did it again just now. No bueno. Nothing happens when I press the button.
Is this feature dependent on any particular model or preconditions to generate the message?

Is the button related to the command with the same name?
I restart everything and it still doesn’t work. The only thing I did between the versions I toggled some models and features.

Hey, here’s new information about this:

Generate commit message does not work in dev container :rotating_light:

I don’t think .cursorules work in dev container either - it’s more like it sometimes work and sometimes does not.

Having the same (similar?) issue in 0.44.11.

Environment:

Version: 0.44.11
VSCode Version: 1.93.1
Commit: fe574d0820377383143b2ea26aa6ae28b3425220
Date: 2025-01-03T07:59:06.361Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.26100

The Sparkle button is replaced by “…”, and the “Generate Commit Message” menu option does nothing.

If I try using the command palette “Generate Commit Message”, I get a “No contents found”, although having staged files.

I’ve got exactly same version and I do see the sparkle icon inside and outside dev container.

Inside dev container the button does nothing, while it works if I open the files locally. The working files are shared from local filesystem.

I’m mainly working with Ruby dev containers.

Generating of commit messages in dev containers has been fixed in Version: 0.45.3 :tada::pray:t2: