# \[BUG\] Antigravity commit generation uses unstaged changes for context for commit generation messages

**URL:** <https://discuss.ai.google.dev/t/bug-antigravity-commit-generation-uses-unstaged-changes-for-context-for-commit-generation-messages/113483>\
**Category:** Google Antigravity\
**Tags:** bug, ai, github\
**Created:** [December 28, 2025, 8:08pm UTC](https://discuss.ai.google.dev/t/bug-antigravity-commit-generation-uses-unstaged-changes-for-context-for-commit-generation-messages/113483 "2025-12-28T20:08:36Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![Nick\_Youngblut](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/nick_youngblut/32/32319_2.png) [@Nick\_Youngblut](https://discuss.ai.google.dev/u/Nick_Youngblut)\
**Post date:** [May 12, 2026, 3:12pm UTC](https://discuss.ai.google.dev/t/bug-antigravity-commit-generation-uses-unstaged-changes-for-context-for-commit-generation-messages/113483/13 "2026-05-12T15:12:36Z")

</div>

I’m seeing the same issue. Antigravity’s commit message generator appears to inspect both staged and unstaged tracked files, rather than only the staged diff. This produces inaccurate commit messages whenever I have unrelated work-in-progress changes in the working tree.

**Please update Antigravity to match the functionality of the Cursor IDE.**

**Expected behavior:**  
Commit message generation should be based only on staged changes, equivalent to `git diff --cached` / `git diff --staged`.

**Actual behavior:**  
The generated message includes context from unstaged files, causing the message to describe changes that will not be included in the commit.

**Additional issue:**  
The generated messages are also much too terse, especially for larger commits. For multi-file or large staged diffs, the generator should produce a more informative message with an appropriate summary and, when warranted, a short body describing the major change groups.

**Impact:**  
I have to generate commit messages via the coding agent, which is slow and overkill.

**Note:**  
I would provide this feedback directly via the Antigravity IDE feedback forum, but that feature doesn’t work: [Unable to provide feedback from antigravity](https://discuss.ai.google.dev/t/unable-to-provide-feedback-from-antigravity/140284)

---

_[View the full topic](https://discuss.ai.google.dev/t/bug-antigravity-commit-generation-uses-unstaged-changes-for-context-for-commit-generation-messages/113483)._