I can’t see my dashboard data on the Overview tab. It is not the first time it happens, it was fixed before but came back. It is reproduced on every device, even devices that have never logged in.
It shows a “Get Started with Cursor” message, even though I have been using Cursor for more than a year and never stopped using it.
Mostly Auto, I have the unlimited version, could be the reason.
Additional Information
Another user have a theory that using a third party dashboard (https://cursortokens.vercel.app) can be the reason because it uses the same cookies. But for him Cursor dashboard works on any other device that haven’t used the dashboard, mine doesn’t work no matter what device I use, even after re-login.
Thanks for the screenshots. This is clearly a backend issue with your account.
The Statsig errors (“Failed to parse data”, “StatsigUser not found”) plus the 500 on /dashboard point to an account data problem on our side. It’s especially weird that it happens even in Incognito and on all devices, so it’s not related to cookies or cache.
I think I’ve been able to track this down, and it actually has nothing to do with Unlimited Auto!
It looks like you’re a member of a “ghost team” that was created but never subscribed to a team plan, and you’re now on a paid individual plan. This causes the queries driving these analytics to fail to find the data for your individual plan.
Hey @MBarella — good news, this one’s fixed on our end!
The root cause turned out to be exactly what Colin tracked down: your account was tied to a “ghost team” (a team that was created but never subscribed), which caused the dashboard’s queries to look for your activity under the wrong account and come back with all zeros — hence the empty graph and the “Get Started” message. We’ve corrected how those queries resolve your data, and the fix is now live.
Could you give https://cursor.com/dashboard a fresh reload (no client update needed — this was a server-side change) and confirm your real activity is showing up? If it’s still empty for you, reply here, and we’ll dig back in.