[GH-ISSUE #440] Fugitive support #164

New issue

Open

opened 2026-03-02 04:12:28 +03:00 by kerem · 3 comments

kerem commented

2026-03-02 04:12:28 +03:00

Owner

Originally created by @jmbeach on GitHub (Feb 2, 2026).
Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/440

This is meant to be more of a discussion post.

For some reason, git-ai isn't working with the vim/nvim git plugin fugitive. I can't figure out why.

Fugitive even has support for a variable g:fugitive_git_executable, but even when that's directly set to my git-ai binary, I lose my AI data when I commit with fugitive and everything gets attributed to me instead of the ai.

Originally created by @jmbeach on GitHub (Feb 2, 2026). Original GitHub issue: https://github.com/git-ai-project/git-ai/issues/440 This is meant to be more of a discussion post. For some reason, git-ai isn't working with the vim/nvim git plugin [fugitive](https://github.com/tpope/vim-fugitive). I can't figure out why. Fugitive even has support for a variable `g:fugitive_git_executable`, but even when that's directly set to my git-ai binary, I lose my AI data when I commit with fugitive and everything gets attributed to me instead of the ai.

kerem commented

2026-03-02 04:12:29 +03:00

Author

Owner

@svarlamov commented on GitHub (Feb 2, 2026):

Hey @jmbeach! Always excited to help get more support for git clients!

When you tried pointing g:fugitive_git_executable at git-ai which path did you use? Was it ~/.git-ai/bin/git or ~/.git-ai/bin/git-ai? I believe it should be the former in this case (this is our symlinked git exec path)

@svarlamov commented on GitHub (Feb 2, 2026): Hey @jmbeach! Always excited to help get more support for git clients! When you tried pointing `g:fugitive_git_executable` at `git-ai` which path did you use? Was it `~/.git-ai/bin/git` or `~/.git-ai/bin/git-ai`? I believe it should be the former in this case (this is our symlinked git exec path)

kerem commented

2026-03-02 04:12:29 +03:00

Author

Owner

@jmbeach commented on GitHub (Feb 2, 2026):

Thanks for the quick reply! It’s the former. I haven’t ruled out that fugitive isn’t doing something more than just running git commit, but it’s so strange. I (read “Claude”) even added a --is-git-ai flag to the source and I was able to verify that :G --is-git-ai returns true

@jmbeach commented on GitHub (Feb 2, 2026): Thanks for the quick reply! It’s the former. I haven’t ruled out that fugitive isn’t doing something more than just running git commit, but it’s so strange. I (read “Claude”) even added a `--is-git-ai` flag to the source and I was able to verify that `:G --is-git-ai` returns true

kerem commented

2026-03-02 04:12:29 +03:00

Author

Owner

@svarlamov commented on GitHub (Feb 3, 2026):

Huh... That's very odd indeed... Is there any way to run fugitive in debug mode to see the git commands it's running and what their outputs are?

Also, are you using worktrees for this by any chance? We have an open PR to get full worktree support in asap

@svarlamov commented on GitHub (Feb 3, 2026): Huh... That's very odd indeed... Is there any way to run fugitive in debug mode to see the git commands it's running and what their outputs are? Also, are you using worktrees for this by any chance? We have an open PR to get full worktree support in asap