Git commit via IDE fails

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Committing via Source Control with the commit editor tab (git-editor.sh / git.useEditorAsCommitInput) fails with HTTP 500. I have used this workflow for previously whithout issue; it stopped working around 2026-06-28, shortly after a Cursor update.

Git output (from Cursor Source Control / Git log):

git -c user.useConfigOnly=true commit --quiet
Error: Bad status code: 500
at ClientRequest. (…/extensions/git/dist/git-editor-main.js:1:1273)

error: There was a problem with the editor ‘“…\AppData\Local\Programs\cursor\resources\app\extensions\git\dist\git-editor.sh”’.
Please supply the message using either -m or -F option.
The internal HTTP handler used by git-editor-main.js returns 500 before COMMIT_EDITMSG can be read/written, so the commit aborts.

Commits from the integrated terminal work: git commit -m “message” completes successfully. Only the UI commit-editor path fails.

Steps to Reproduce

Ensure git.useEditorAsCommitInput is enabled (my normal workflow).
Open any git repo in Cursor on Windows.
Stage changes in Source Control.
Commit with an empty inline message box so Cursor opens the commit editor tab (or use the flow that invokes git-editor.sh).
Observe HTTP 500 and failed commi

Expected Behavior

Commit editor tab opens; I write a multi-line message, save/close; commit completes (as before 2026-06-27).

Operating System

Windows 10/11

Version Information

Cursor: 3.9.16
VS Code base: 1.105.1
Commit: 042b3c1a4c53f2c3808067f519fbfc67b72cad80
Build date: 2026-06-27T06:41:01.941Z

Additional Information

Git: 2.45.1.windows.1
core.editor: not set in git config (Cursor injects git-editor.sh at commit time)
No pre-commit hooks in the affected repo
Git user identity is configured
Terminal commit works: git commit -m “…” succeeds from Cursor’s integrated terminal and from an external shell

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hi @DaveKP,

I thought I was able to reproduce this yesterday (on Mac, rather than Windows), but after a fresh git pull and restarting Cursor, it started working again.

Could you confirm whether the issue persists in a new Git repository (or another project) and after restarting Cursor?