This is a known bug. The setup checklist currently only checks team-based environments to determine completion, so for individual accounts (without a team), it never recognizes your cloud agent setup as complete — even though everything is working fine.
Your cloud agents are fully functional. This is purely a UI issue with the checklist detection. Our team is actively working on the fix. You can safely ignore that step
I need to check my biling and usage to see how many credit left.
Nothing I can do if this UI bugs exist.
I guest what I can do just stop the subscription from Link till it fixed.
If you first navigate to https://cursor.com/en-US/dashboard/spending (or any en-US locale URL), the redirect stops. After that, even navigating to the non-locale URL https://cursor.com/dashboard/spending works fine without triggering the redirect.
2Ways to reproduce the original bug:
Clear your cookies of cursor sites
Navigate directly to https://cursor.com/zh-Hant/dashboard/spending (or any zh-Hant locale URL)
It looks like the Getting Started redirect is only triggered when the dashboard is first loaded under the zh-Hant locale. Switching to en-US first seems to set a session state that prevents the redirect from firing again.
Quick fix: just use the en-US URL directly when accessing the dashboard.
This might be the page-routing issue on SPA structure or something.
The bug didn’t really been fixed yet.
Thanks for the video, @JiangGan. This is a different bug from the original checklist issue - it’s a locale-routing problem where the dashboard redirects all navigation back to Overview when your browser language is set to Traditional Chinese (zh-Hant).
@Lefioty - great find on the workaround and root cause identification.
Quick fix: navigate to https://cursor.com/en-US/dashboard/usage first (or move English to the top of your browser’s language preferences). After that, normal navigation works.
Since this is a separate issue from the original thread, could you open a new thread for it if still any blockers? That way our team can track the locale redirect bug properly. Include: