Commit and push minor issue

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Ability to Commit and push without a commit message

Steps to Reproduce

just try to make any changes to an open repo, Try to manually commit and push without a commit message and it’ll give you a status code 500

Expected Behavior

It should be greyed out, Like unclickable until a commit message is typed.

Screenshots / Screen Recordings

Screenshot 2026-07-27 004805.png
Screenshot 2026-07-27 004805.png296×161 4.58 KB

Operating System

Windows 10/11

Version Information

Version: 3.13.10 (user setup)
VS Code Extension API: 1.128.0
Commit: 4f02290ccd9304f0e6bf8ee85f6e9106f02ac1f0
Date: 2026-07-23T21:41:07.333Z
Layout: IDE
Build Type: Stable
Release Track: Default
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.256
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

Hey, thanks for the report. A couple of things.

The button isn’t greyed out on purpose. An empty commit message is meant to open a separate editor tab where you write the message, not block the button. That behavior comes from upstream VS Code. So “grey it out” is more of a feature request than a bug.

But the status code 500 is a real bug. On some machines, the handoff to the commit message editor fails instead of opening the tab. We’ve seen this from other users too on Windows and Linux.

For now, either workaround should help:

  • Type the commit message in the Source Control input box before committing. This skips the editor and commits via -m.
  • Or disable using the editor for commit input. In settings, set git.useEditorAsCommitInput: false.

Let me know if you still get 500 even with a non-empty message, and we’ll dig deeper.

7

I’ve tried commiting with no message in Source Control using the IDE and no commit window pops, On VSCode and VSCodium it shows, But not on Cursor.