AI commit message generation outputs "Sure! PI" instead of actual message for first commit

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When clicking “Generate commit message” for the first commit, it outputs “Sure! PI” instead of a proper message like “Initial commit”

Steps to Reproduce

  1. Create a new project
  2. Add a file (e.g., README.md)
  3. Stage the file
  4. Click :sparkles: (Generate commit message)

Expected Behavior

A meaningful commit message like “Initial commit” or “Add README.md”

Screenshots / Screen Recordings

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.43
VSCode Version: 1.105.1
Commit: 32cfbe848b35d9eb320980195985450f244b3030
Date: 2025-12-19T06:06:44.644Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.0.0

For AI issues: which model did you use?

Default/Auto

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. I can see in your screenshot that the generator returned “Sure! PI” instead of a proper message on the first commit.

It looks like this happens because the first commit has no Git history for the generator to analyze. The generator pulls from:

  • The current changes (you do have them, like the new README.md)
  • The project’s Git history (missing on the first commit)

Without any history, the model can sometimes produce odd output.

For now, please try:

  • Write the message manually for this first commit
  • For the next commits, the generator should work normally once there’s history
  • Or use Chat: open Chat, type @Commit (Diff of Working State), and ask “generate a proper commit message”. This often works better than the built-in generator

I’ll pass this to the team. This should definitely be handled better for first commits in new projects.

Thanks, Dean. That explains why it output “Sure! PI”. I’ll stick to writing the first commit manually for now. Looking forward to seeing a fix for new projects in the future!

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.