Hey, thanks for confirming the bug is still happening on 3.5.17. It’s the same issue as in Generate Commit Message: No contents found. The internal git provider loses its registration after Cursor has been running for a while, so the feature stops seeing staged files.
This is on our side and it’s logged internally. I can’t share an ETA for a fix yet.
Current workaround:
When it happens, restart Cursor. After a restart, Generate Commit Message works again.
If you want it to last longer, start Cursor with a clean profile cursor --user-data-dir=/tmp/cursor-test. This resets the state.
If, when it happens, you see fresh red errors in the Developer Tools Console via Help → Toggle Developer Tools right when you click the button, not startup errors, please post a screenshot here. That’ll help the team narrow down the cause.