I’ve noticed that the Сurso Tab auto-suggestions have recently become less effective: they’ve become sluggish and don’t display suggestions in at least 4 out of 5 cases.
While I used to be able to start typing and the suggestion would appear immediately, now it simply doesn’t work. Or rather, it does work, but really rarely.
Steps to Reproduce
If the context of changes in the code editor is already set, for example:
const a = 1;
constastart typing const c = a +
then auto-completion will likely not work.
Additionally, suggestions for file imports do not work.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Hey @Vadim-Kul, that definitely sounds frustrating, especially when Cursor Tab is often known as Cursor’s strongest features. (At least that’s how vocal Cursor pro users have been about it, and with their recent improvements using a online-based new RL model, it should be better)
It looks like there are two separate symptoms: the suggestions sometimes don’t appear at all, and when they do they’re often low‑quality. We can try a couple of quick checks.
Make sure the Cursor Tab is enabled for the file
In the editor’s bottom‑right corner you’ll see the “Cursor Tab” button. Click it and verify that it’s on (not disabled). If it’s off, enable it and try typing again.
Test in a different project
Open a fresh folder (or create a new simple project) and see if the auto‑suggestions work there. If they do, the problem is likely tied to something in the original project.
Copy the problematic project to a new location
Duplicate the whole project folder to another path, open that copy in Cursor, and check whether the issue persists. Cursor treats that as a new project, and can behave differently because it’s at a new location - so that’s worth checking!
A couple of quick questions to narrow it down further:
Does the problem happen for all file types, or only for specific languages (e.g., JavaScript/TypeScript)?
Are any Cursor extensions installed? If so, you can try running cursor --disable-extensions to see if that changes the behavior.
Let me know what you find after these steps; we can dig deeper from there.
I have Cursor Tab enabled. I’m seeing this issue in other repositories I work with. Also, when I create a new .js file in a different folder and start typing, autocomplete doesn’t work either.
I work with JavaScript/TypeScript, so unfortunately I can’t comment on other languages.
Console errors
Open Help → Toggle Developer Tools, go to the Console tab. Do any errors appear when autocomplete should fire?
Network environment
Are you behind a VPN or proxy? If so, try connecting to a different network (e.g., a mobile hotspot) and see if the Tab suggestions return.
Network diagnostics
Go to Cursor Settings → Network → Run Diagnostics. Let me know if the results are all green.
Disable HTTP/2
In Cursor Settings → Network, enable Disable HTTP/2 (so Cursor falls back to HTTP 1.1), then restart Cursor. Does autocomplete work after that?
Agent functionality - would be great to know
Does the Agent chat window work as expected, or is it also affected?
If you’ve already tried cursor --disable-extensions, let me know the outcome as well.
It seems that enabling the VPN and the HTTP/2 to HTTP/1.1 switch both worked, even though the HTTP/2 diagnostics showed all green! (Agent chat window worked as expected btw)
Great to hear that switching to HTTP/1.1 got things working. Cursor uses HTTP/2 bidirectional streaming by default for real‑time chat and agent experiences, which I guess includes the Tab agent. In networks where HTTP/2 streaming fails, Cursor falls back to HTTP/1.1 Server‑Side Events (SSE) automatically. Since the fallback isn’t triggered for the Tab completion for some reason, staying on HTTP/1.1 is currently the most reliable workaround at this point.
