# Bug Finder always fails with the message "Failed to parse git show output"

**URL:** <https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519>\
**Category:** Bug Reports\
**Created:** [January 6, 2025, 8:45pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519 "2025-01-06T20:45:04Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![TacoNavigator](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/taconavigator/32/3271_2.png) [@TacoNavigator](https://forum.cursor.com/u/TacoNavigator)\
**Post date:** [January 6, 2025, 8:45pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/1 "2025-01-06T20:45:04Z")

</div>

I’m on Windows 10 using Cursor 0.44.11.

Steps to reproduce:

1. open ANY project in Cursor (big or small, many changes or few, doesn’t seem to matter)
2. open the bug finder tab and click “run new”
3. in the preview dialog, it will correctly list the changed files and give you a quote for the price and whether or not you can do a free run (i haven’t tried changing anything in the advanced configuration, those are all at their default values)
4. try to start a bug finder run (free or paid, doesn’t matter)
5. it immediately fails, saying “Failed to parse git show output”

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/1/5/15272cca14390dd10610041111b7fb443b125e99.png)

What happens if I run “git show” manually? I see a diff of the latest commit that basically looks how I would expect. Notably though, it opens with the git pager, so i have to press Q to exit this command.

---

<div class="post-metadata">

**Author:** ![tchenazure](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/tchenazure/32/18817_2.png) [@tchenazure](https://forum.cursor.com/u/tchenazure)\
**Post date:** [January 7, 2025, 7:26am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/2 "2025-01-07T07:26:28Z")

</div>

I was facing the exactly same issue.

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [January 7, 2025, 11:48am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/3 "2025-01-07T11:48:37Z")

</div>

Hey, thanks for the report!

It’s possible that, as you suggested, git attempts to open the result of `git show` in the interactive pager, which is stopping Cursor from being able to parse it.  
Does anything change if you set Git to not use the pager (then restart all Cursor instances to ensure the config change is loaded): `git config --global core.pager "cat"`

I have reported this to the team regardless, who will hopefully fix this in a future update!

---

<div class="post-metadata">

**Author:** ![TacoNavigator](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/taconavigator/32/3271_2.png) [@TacoNavigator](https://forum.cursor.com/u/TacoNavigator)\
**Post date:** [January 7, 2025, 10:22pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/4 "2025-01-07T22:22:47Z")

</div>

Hey @danperks, thanks for the reply!

I just tried it, but unfortunately that doesn’t fix the issue. Bug Finder still fails with the same message. I’ve made sure to restart Cursor after changing that git config option and confirmed that running “git show” in the Cursor terminal now shows its result without using the pager.

Hopefully the team can figure out what’s really causing this issue, or if not, maybe tell them to make the error message more detailed?

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [January 8, 2025, 7:36pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/5 "2025-01-08T19:36:52Z")

</div>

Thanks for clarifying. I have passed it on, so hopefully they’re looking into it as we speak!

---

<div class="post-metadata">

**Author:** ![vmysla](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/vmysla/32/19654_2.png) [@vmysla](https://forum.cursor.com/u/vmysla)\
**Post date:** [January 11, 2025, 8:23pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/6 "2025-01-11T20:23:00Z")

</div>

the same issue for me

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/c/7c4e99df28ce537a988099373f4acec2c79a0694.png)

---

<div class="post-metadata">

**Author:** ![nbmbr3](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/nbmbr3/32/11488_2.png) [@nbmbr3](https://forum.cursor.com/u/nbmbr3)\
**Post date:** [January 13, 2025, 9:33am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/7 "2025-01-13T09:33:11Z")

</div>

Experiencing the same problem with the bug finder issue.

---

<div class="post-metadata">

**Author:** ![simi2525](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/simi2525/32/24180_2.png) [@simi2525](https://forum.cursor.com/u/simi2525)\
**Post date:** [February 4, 2025, 10:02am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/8 "2025-02-04T10:02:04Z")

</div>

I encountered the same issue both with and without the git show cat configuration

---

<div class="post-metadata">

**Author:** ![danperks](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/danperks/32/19087_2.png) [@danperks](https://forum.cursor.com/u/danperks)\
**Post date:** [February 6, 2025, 12:14am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/9 "2025-02-06T00:14:14Z")

</div>

What happens when you run both commands yourself, does the output work as expected?

---

<div class="post-metadata">

**Author:** ![Araa](https://avatars.discourse-cdn.com/v4/letter/a/e274bd/32.png) [@Araa](https://forum.cursor.com/u/Araa)\
**Post date:** [February 9, 2025, 10:55am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/10 "2025-02-09T10:55:56Z")

</div>

I am also facing this issue on 0.45.11 on Windows.

Each failed run causes output like this in `Cursor\logs\...\window1\exthost\vscode.git\Git.log`:

```auto
2025-02-09 11:45:59.206 [info] > git merge-base origin/master HEAD [34ms]
2025-02-09 11:45:59.264 [info] > git diff --no-color --ignore-space-change -U50 55cf83762d4af0442ec5a645d2808154a3b48888 [56ms]
2025-02-09 11:46:01.795 [info] > git rev-parse --show-toplevel [32ms]
2025-02-09 11:46:01.795 [info] fatal: not a git repository (or any of the parent directories): .git

```

Running the failing command in good ole cmd yields:

```auto
C:\Users\me\myrepo>git rev-parse --show-toplevel
C:/Users/me/myrepo

C:\Users\me\myrepo>

```

Full log file shows a mixed bag of failing and succeeding git commands:

```auto
2025-02-09 11:49:00.695 [info] [main] Log level: Info
2025-02-09 11:49:00.695 [info] [main] Validating found git in: "C:\Program Files\Git\cmd\git.exe"
2025-02-09 11:49:00.695 [info] [main] Using git "2.47.1.windows.2" from "C:\Program Files\Git\cmd\git.exe"
2025-02-09 11:49:00.695 [info] [Model][doInitialScan] Initial repository scan started
2025-02-09 11:49:00.761 [info] > git rev-parse --show-toplevel [70ms]
2025-02-09 11:49:00.826 [info] > git rev-parse --git-dir --git-common-dir [45ms]
2025-02-09 11:49:00.837 [info] [Model][openRepository] Opened repository: c:\Users\me\myrepo
2025-02-09 11:49:00.885 [info] > git config --get commit.template [43ms]
2025-02-09 11:49:00.887 [info] > git rev-parse --show-toplevel [43ms]
2025-02-09 11:49:00.887 [info] fatal: not a git repository (or any of the parent directories): .git
2025-02-09 11:49:00.898 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/master refs/remotes/master [44ms]
2025-02-09 11:49:01.094 [info] > git status -z -uall [191ms]
2025-02-09 11:49:01.095 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [188ms]
2025-02-09 11:49:01.108 [info] > git rev-parse --show-toplevel [218ms]
2025-02-09 11:49:02.112 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/master refs/remotes/master [1006ms]
2025-02-09 11:49:02.321 [info] > git config --local branch.master.vscode-merge-base [204ms]
2025-02-09 11:49:02.321 [warning] [Git][config] git config failed: Failed to execute git
2025-02-09 11:49:02.325 [info] > git rev-parse --show-toplevel [219ms]
2025-02-09 11:49:02.326 [info] > git config --get commit.template [223ms]
2025-02-09 11:49:02.326 [info] > git fetch [1489ms]
2025-02-09 11:49:02.326 [info] Missing or invalid credentials.
Skip silent fetch commands
git@github.com: Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists.
2025-02-09 11:49:02.433 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/master refs/remotes/master [78ms]
2025-02-09 11:49:02.433 [info] > git reflog master --grep-reflog=branch: Created from *. [109ms]
2025-02-09 11:49:02.438 [info] > git config --get commit.template [95ms]
2025-02-09 11:49:02.438 [info] > git rev-parse --show-toplevel [97ms]
2025-02-09 11:49:02.450 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/master refs/remotes/master [78ms]
2025-02-09 11:49:02.515 [info] > git rev-parse --show-toplevel [65ms]
2025-02-09 11:49:02.516 [info] > git symbolic-ref --short refs/remotes/origin/HEAD [78ms]
2025-02-09 11:49:02.516 [info] fatal: ref refs/remotes/origin/HEAD is not a symbolic ref
2025-02-09 11:49:02.516 [warning] [Repository][getDefaultBranch] Failed to get default branch details: Failed to execute git.
2025-02-09 11:49:02.540 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/master refs/remotes/master [75ms]
2025-02-09 11:49:02.545 [info] > git status -z -uall [74ms]
2025-02-09 11:49:02.552 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [77ms]
2025-02-09 11:49:02.572 [info] > git merge-base refs/heads/master refs/remotes/origin/master [51ms]
2025-02-09 11:49:02.595 [info] > git rev-parse --show-toplevel [56ms]
2025-02-09 11:49:02.619 [info] > git config --local branch.master.vscode-merge-base [76ms]
2025-02-09 11:49:02.620 [warning] [Git][config] git config failed: Failed to execute git
2025-02-09 11:49:02.625 [info] > git merge-base refs/heads/master refs/remotes/origin/master [65ms]
2025-02-09 11:49:02.697 [info] > git diff --name-status -z --diff-filter=ADMR 55cf83762d4af0442ec5a645d2808154a3b48888...refs/remotes/origin/master [69ms]
2025-02-09 11:49:02.698 [info] > git rev-parse --show-toplevel [79ms]
2025-02-09 11:49:02.698 [info] > git diff --name-status -z --diff-filter=ADMR 55cf83762d4af0442ec5a645d2808154a3b48888...refs/remotes/origin/master [121ms]
2025-02-09 11:49:02.716 [info] > git check-ignore -v -z --stdin [117ms]
2025-02-09 11:49:02.717 [info] > git reflog master --grep-reflog=branch: Created from *. [95ms]
2025-02-09 11:49:02.758 [info] > git rev-parse --show-toplevel [42ms]
2025-02-09 11:49:02.763 [info] > git symbolic-ref --short refs/remotes/origin/HEAD [43ms]
2025-02-09 11:49:02.763 [info] fatal: ref refs/remotes/origin/HEAD is not a symbolic ref
2025-02-09 11:49:02.763 [warning] [Repository][getDefaultBranch] Failed to get default branch details: Failed to execute git.
2025-02-09 11:49:02.800 [info] > git rev-parse --show-toplevel [39ms]
2025-02-09 11:49:02.845 [info] > git rev-parse --show-toplevel [42ms]
2025-02-09 11:49:02.893 [info] > git rev-parse --show-toplevel [45ms]
2025-02-09 11:49:02.935 [info] > git rev-parse --show-toplevel [39ms]
2025-02-09 11:49:02.977 [info] > git rev-parse --show-toplevel [39ms]
2025-02-09 11:49:02.979 [info] [Model][doInitialScan] Initial repository scan completed - repositories (1), closed repositories (0), parent repositories (0), unsafe repositories (0)
2025-02-09 11:49:04.157 [info] > git symbolic-ref --short refs/remotes/origin/HEAD [34ms]
2025-02-09 11:49:04.157 [info] fatal: ref refs/remotes/origin/HEAD is not a symbolic ref
2025-02-09 11:49:04.193 [info] > git rev-parse --verify origin/master [32ms]
2025-02-09 11:49:04.230 [info] > git merge-base origin/master HEAD [34ms]
2025-02-09 11:49:04.293 [info] > git diff --no-color --ignore-space-change -U50 55cf83762d4af0442ec5a645d2808154a3b48888 [58ms]
2025-02-09 11:49:05.210 [info] > git config --get commit.template [37ms]
2025-02-09 11:49:05.214 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/master refs/remotes/master [40ms]
2025-02-09 11:49:05.258 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [38ms]
2025-02-09 11:49:05.259 [info] > git status -z -uall [43ms]
2025-02-09 11:49:20.124 [info] > git config --get commit.template [43ms]
2025-02-09 11:49:20.126 [info] > git for-each-ref --format=%(refname)%00%(upstream:short)%00%(objectname)%00%(upstream:track)%00%(upstream:remotename)%00%(upstream:remoteref) --ignore-case refs/heads/master refs/remotes/master [43ms]
2025-02-09 11:49:20.179 [info] > git for-each-ref --sort -committerdate --format %(refname) %(objectname) %(*objectname) [48ms]
2025-02-09 11:49:20.182 [info] > git status -z -uall [53ms]
2025-02-09 11:49:20.212 [info] > git rev-parse --show-toplevel [41ms]
2025-02-09 11:49:20.212 [info] fatal: not a git repository (or any of the parent directories): .git
2025-02-09 11:49:48.895 [info] > git log --format=%H%n%aN%n%aE%n%at%n%ct%n%P%n%D%n%B -z --shortstat --diff-merges=first-parent -n50 --skip=0 --topo-order --decorate=full --stdin [298ms]
2025-02-09 11:49:49.294 [info] > git check-ignore -v -z --stdin [41ms]
2025-02-09 11:49:50.510 [info] > git log --format=%H%n%aN%n%aE%n%at%n%ct%n%P%n%D%n%B -z --shortstat --diff-merges=first-parent -n50 --skip=0 --topo-order --decorate=full --stdin [304ms]
2025-02-09 11:50:40.876 [info] > git merge-base origin/master HEAD [34ms]
2025-02-09 11:50:40.935 [info] > git diff --no-color --ignore-space-change -U50 55cf83762d4af0442ec5a645d2808154a3b48888 [54ms]
2025-02-09 11:50:43.591 [info] > git rev-parse --show-toplevel [39ms]
2025-02-09 11:50:43.591 [info] fatal: not a git repository (or any of the parent directories): .git
2025-02-09 11:50:49.237 [info] > git merge-base origin/master HEAD [34ms]
2025-02-09 11:50:49.294 [info] > git diff --no-color --ignore-space-change -U50 55cf83762d4af0442ec5a645d2808154a3b48888 [54ms]

```

---

<div class="post-metadata">

**Author:** ![springjazzy](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/springjazzy/32/17104_2.png) [@springjazzy](https://forum.cursor.com/u/springjazzy)\
**Post date:** [February 10, 2025, 12:21pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/11 "2025-02-10T12:21:10Z")

</div>

It seems that I’m late for the party - didn’t find AI code review feature since it was modified into Bug Finder already. Anyway, I’m also facing same error - regardless of whether git pager is enabled or not. I’ve copy-pasted changes into cursor notepad and asked AI to find errors and also summarize meaning of changes in referenced notepad. Wondering - Does Bug Finder gives you more than that?

---

<div class="post-metadata">

**Author:** ![Artrix](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/artrix/32/30717_2.png) [@Artrix](https://forum.cursor.com/u/Artrix)\
**Post date:** [February 27, 2025, 4:11am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/12 "2025-02-27T04:11:26Z")

</div>

Exactly the same here.

---

<div class="post-metadata">

**Author:** ![snorlaxo](https://avatars.discourse-cdn.com/v4/letter/s/ecc23a/32.png) [@snorlaxo](https://forum.cursor.com/u/snorlaxo)\
**Post date:** [February 28, 2025, 12:00pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/13 "2025-02-28T12:00:27Z")

</div>

Same error

---

<div class="post-metadata">

**Author:** ![ninjazan420](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/ninjazan420/32/33200_2.png) [@ninjazan420](https://forum.cursor.com/u/ninjazan420)\
**Post date:** [March 8, 2025, 5:50pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/14 "2025-03-08T17:50:45Z")

</div>

still an issue

---

<div class="post-metadata">

**Author:** ![ceseshi](https://avatars.discourse-cdn.com/v4/letter/c/54ee81/32.png) [@ceseshi](https://forum.cursor.com/u/ceseshi)\
**Post date:** [March 26, 2025, 12:46pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/15 "2025-03-26T12:46:13Z")

</div>

Same here, I’d love to try that feature

---

<div class="post-metadata">

**Author:** ![michael-meetkai](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/michael-meetkai/32/45807_2.png) [@michael-meetkai](https://forum.cursor.com/u/michael-meetkai)\
**Post date:** [April 10, 2025, 3:09am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/16 "2025-04-10T03:09:39Z")

</div>

Same issue

---

<div class="post-metadata">

**Author:** ![raythurnvoid](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/raythurnvoid/32/7302_2.png) [@raythurnvoid](https://forum.cursor.com/u/raythurnvoid)\
**Post date:** [April 22, 2025, 3:33pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/17 "2025-04-22T15:33:50Z")

</div>

Still broken today

---

<div class="post-metadata">

**Author:** ![MuslimDevHamid](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/muslimdevhamid/32/55160_2.png) [@MuslimDevHamid](https://forum.cursor.com/u/MuslimDevHamid)\
**Post date:** [May 14, 2025, 5:09pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/18 "2025-05-14T17:09:37Z")

</div>

Still same issue

---

<div class="post-metadata">

**Author:** ![liquefy](https://avatars.discourse-cdn.com/v4/letter/l/edb3f5/32.png) [@liquefy](https://forum.cursor.com/u/liquefy)\
**Post date:** [May 14, 2025, 7:17pm UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/19 "2025-05-14T19:17:59Z")

</div>

still having this issue as well

---

<div class="post-metadata">

**Author:** ![evan-boissonnot](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/evan-boissonnot/32/55659_2.png) [@evan-boissonnot](https://forum.cursor.com/u/evan-boissonnot)\
**Post date:** [May 16, 2025, 9:17am UTC](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519/20 "2025-05-16T09:17:17Z")

</div>

Still prob here, I am on Windows 10.  
with a very small project

[Next page](https://forum.cursor.com/t/bug-finder-always-fails-with-the-message-failed-to-parse-git-show-output/39519.md?page=2)