I’ve tested cleaning profile in last week. Basically it works, but not for long. After few hours problem start occurring again.
git status - works as expected. I’ve seen stagged files
Git: Show Git Output - after cleaning profile it works, but when error occurs I havent seen anything in console.
Hey, thanks for the extra info. The fact that a clean profile helps temporarily but then breaks again is an important detail. It sounds like Cursor’s internal git provider is disconnecting over time.
We need to catch it when the error shows up again. When it happens next time before restarting Cursor:
Open Developer Tools and go to the Console tab
Check for red errors, especially anything mentioning git, commit, EverythingProvider, or cursor-commits
Send a screenshot or paste the text of those errors here
Also, do you have any git-related extensions installed like GitLens, Git Graph, etc.? If yes, try disabling them and use Cursor for a couple of hours. Let’s see if they’re triggering the issue.
Regarding installed extensions - I’ve only GitLens — Git superchargedv17.11.1 (disabled for now).
I’ve also observed one error after restarting cursor, but I dont know if it is somehow related to my issue.
workbench.desktop.main.js:44025 [KnowledgeBaseService] Error fetching git upstream URL: Error: No full commit provider registered
at Q5a.getGitUpstreamURL (workbench.desktop.main.js:43855:106885)
at fGa.getGitUpstreamUrl (workbench.desktop.main.js:44025:8861)
at fGa.refresh (workbench.desktop.main.js:44025:9183)
I can see the Console screenshots, they’re really helpful.
The key error here is:
[KnowledgeBaseService] Error fetching git upstream URL: Error: No full commit provider registered
This means Cursor’s internal git provider is getting disabled while you’re working. That’s why it works fine on a fresh profile, then breaks after some time. The provider loses its registration.
The other Console errors (Failed to load team commands, HOOKS Failed to parse, TrustedScript) are most likely side effects and not directly related.
The main question now is whether disabling GitLens helped. Please use Cursor with GitLens turned off for at least a day and see if the error comes back. GitLens can conflict with Cursor’s internal git provider.
If the bug returns even without GitLens, let me know and I’ll pass the details to the team.
2 days ago I’ve cleared profile and for most of the time, everything was working until today.
I dont see anything suspicious in console, but maybe you will find something useful.
All messages except last one are showing after running cursor.
Thanks, I see the console screenshot, thanks. Since GitLens didn’t help, it’s most likely a bug on our side where the git provider loses its registration after some time.
One more thing for debugging, if you don’t mind. Next time the error shows up, right at that moment (without restarting Cursor), open the Developer Tools Console and check if there are any new red errors. What’s in the screenshot now looks like startup errors, but we need to catch the moment when the provider disconnects.
Specifically, open Console, click the generate commit button, and send me any new errors that appear at that moment.
Hi Dean,
I haven’t seen anything new since our last conversation. The only error which mostly showed up is Failed to generate commit message: No contents found.
But I’ve noticed that when I type commit message and this error is showing up, I’ve some small delay until letters show up. Sligthly annoying, but only when you use to see something immediatally
Thanks for the detailed debugging. We’ve pulled everything we can from Console on your side. The bug is that the internal git provider (EverythingProvider) loses its registration after running for a while, and by the time you click, it no longer shows up in the logs. The fact that a clean profile helps temporarily but then the issue comes back matches this.
I’ve filed this internally as a bug on our side, and attached your thread plus the related symptom with input lag. I can’t share an ETA for a fix yet.
One request just in case. You’re on 2.6.22, and there have been a few updates since then. Please update Cursor to the latest stable and let me know if it still reproduces. If it does, the workaround for now is to restart Cursor when the error shows up.
