Gemini Antigravity git commits get misattributed to a stranger

This is a weird one and it's been eating at me. I've been using Gemini Antigravity through the Zed extension to write code, and everything works great until I look at the git history. Antigravity is making commits, which is expected, but the author attribution is completely off.

In Zed's source control panel, the commit looks normal. The author shows as antigravity with the email [email protected] So what's actually happening here? GitHub doesn't use the name field for attribution — it uses the email address in the git commit. If the commit's email matches the email on someone else's GitHub account (even a private/primary email), GitHub will link that commit to their profile. That means [email protected]

This isn't an Antigravity bug per se — it's a git identity configuration issue that's bleeding through the extension. The Zed extension is likely using a default or cached git identity instead of pulling from your local .gitconfig, or it's setting the author to the bot identity but GitHub is resolving that email to the wrong user.

Here's what I'd check next:

1. Verify your local git config : Rungit config user.name andgit config user.email in the repo. If these are set correctly, Antigravity should respect them unless the extension overrides them. The fact that Zed shows[email protected]
2. Check the actual commit metadata : Rungit show --format=full on one of these commits. You'll see both the author and committer fields. My hunch is the author is set toantigravity <[email protected] > by the extension, but your local git config is fine. The problem is purely on GitHub's end matching that email to the wrong account.
3. Override the identity in the extension : Look for a setting in the Zed Antigravity extension for git author configuration. Some AI coding extensions let you specify a custom git identity or choose to commit as yourself rather than the bot. If there's no such setting, you might need to set it via environment variables or a wrapper script.

4. **Rename the bot's email** : If you have control over the Antigravity configuration, changing the commit email from[\[email protected\]](https://promptcube3.com/cdn-cgi/l/email-protection)
[\[email protected\]](https://promptcube3.com/cdn-cgi/l/email-protection)

5. Use signed commits or explicit authorship : If the extension supports it, configuring GPG or SSH signing for commits would at least give you a cryptographic trail pointing back to your key rather than relying on email matching alone.

The git history isn't hard to fix — you can rebase and reset the author, or use git commit --amend --author followed by a force push. But the underlying issue will keep recurring every time Antigravity makes a commit through the extension with that same email.

This is one of those edge cases that highlights how fragile email-based attribution really is in git. The name field is cosmetic, but the email is the real key, and if it collides with someone else's account, there's no way to disambiguate it from the commit alone.

I'm curious if anyone else has run into this with other AI coding agents. Does Claude Code or Copilot have the same issue when they commit through their respective extensions? Or is this specific to how the Zed Antigravity extension handles git identity?

Next Lab Launch Failure: Unraveling the "Failed to Enroll User in Vocareum: 400" Error →

All Replies （0） #

Want a live back-and-forth? Join the global AI chat room — login to talk. No replies yet — be the first!