# Dashboard frequently requires re-login

**URL:** <https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391>\
**Category:** Bug Reports\
**Created:** [June 10, 2025, 12:41pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391 "2025-06-10T12:41:31Z")\
**Posts on this page:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![QTom](https://avatars.discourse-cdn.com/v4/letter/q/b77776/32.png) [@QTom](https://forum.cursor.com/u/QTom)\
**Post date:** [June 10, 2025, 12:41pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/1 "2025-06-10T12:41:31Z")

</div>

> **[Cursor - The AI Code Editor](https://www.cursor.com/en/dashboard)**
>
> Built to make you extraordinarily productive, Cursor is the best way to code with AI.

Dashboard frequently requires re-login

---

<div class="post-metadata">

**Author:** ![Kleyber](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/kleyber/32/41881_2.png) [@Kleyber](https://forum.cursor.com/u/Kleyber)\
**Post date:** [June 10, 2025, 1:00pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/2 "2025-06-10T13:00:52Z")

</div>

Yeah, I’ve noticed that too. It seems they decreased the time of site’s session…

---

<div class="post-metadata">

**Author:** ![QTom](https://avatars.discourse-cdn.com/v4/letter/q/b77776/32.png) [@QTom](https://forum.cursor.com/u/QTom)\
**Post date:** [June 10, 2025, 1:16pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/3 "2025-06-10T13:16:26Z")

</div>

This makes the operation of relying on the webpage to check usage become extremely inconvenient, seriously reducing my work efficiency and contradicting Cursor’s goal

---

<div class="post-metadata">

**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\
**Post date:** [June 10, 2025, 8:23pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/4 "2025-06-10T20:23:17Z")

</div>

There is a “cursor stats” plugin

---

<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:** [June 11, 2025, 10:24am UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/5 "2025-06-11T10:24:06Z")

</div>

Thanks for the feedback. This is done for security, but I admit it is pretty short if you want to keep an eye on your usage!

Will pass to the team!

---

<div class="post-metadata">

**Author:** ![proteus-dev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/proteus-dev/32/51624_2.png) [@proteus-dev](https://forum.cursor.com/u/proteus-dev)\
**Post date:** [June 11, 2025, 11:41am UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/6 "2025-06-11T11:41:09Z")

</div>

thanks, didn’t know about it!  
will give it a try.

> **[Cursor Stats - Visual Studio Marketplace](https://marketplace.visualstudio.com/items?itemName=Dwtexe.cursor-stats)**
>
> Extension for Visual Studio Code - A Cursor extension for monitoring usage.

---

<div class="post-metadata">

**Author:** ![QTom](https://avatars.discourse-cdn.com/v4/letter/q/b77776/32.png) [@QTom](https://forum.cursor.com/u/QTom)\
**Post date:** [June 11, 2025, 11:55am UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/7 "2025-06-11T11:55:08Z")

</div>

Cursor Stats is just a simple statistic. Interestingly, Cursor has just improved with a brand new Dashboard for viewing usage curves and other information, but the way to view it is so convoluted that you have to log in again shortly after

---

<div class="post-metadata">

**Author:** ![volare](https://avatars.discourse-cdn.com/v4/letter/v/7feea3/32.png) [@volare](https://forum.cursor.com/u/volare)\
**Post date:** [June 11, 2025, 12:07pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/8 "2025-06-11T12:07:54Z")

</div>

These security paranoia are really ruinning the experience.  
Please have a check box for user that want to “stay logged” in. So it won’t expire at all or every 15 days.

---

<div class="post-metadata">

**Author:** ![proteus-dev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/proteus-dev/32/51624_2.png) [@proteus-dev](https://forum.cursor.com/u/proteus-dev)\
**Post date:** [June 11, 2025, 12:10pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/9 "2025-06-11T12:10:06Z")

</div>

cursor stats is not what I expected. Doesnt do the job for me.

---

<div class="post-metadata">

**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\
**Post date:** [June 11, 2025, 5:03pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/10 "2025-06-11T17:03:26Z")

</div>

Well, what do you expect? Tell the author 🙂

---

<div class="post-metadata">

**Author:** ![proteus-dev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/proteus-dev/32/51624_2.png) [@proteus-dev](https://forum.cursor.com/u/proteus-dev)\
**Post date:** [June 11, 2025, 5:17pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/11 "2025-06-11T17:17:58Z")

</div>

fair point. given the context of the discussion and the problem we are trying to solve and the solution that has been proposed in this problem-solution context:  
I was looking for a stats monitor that shows me how many requests I’ve used so far.

---

<div class="post-metadata">

**Author:** ![leoing](https://avatars.discourse-cdn.com/v4/letter/l/dec6dc/32.png) [@leoing](https://forum.cursor.com/u/leoing)\
**Post date:** [June 11, 2025, 10:04pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/12 "2025-06-11T22:04:40Z")

</div>

![image](https://us1.discourse-cdn.com/cursor1/original/3X/9/a/9aa89132ed8e2686e14ace04ab7dcc20a9f1ec93.png)  
Lower right corner

---

<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:** [June 11, 2025, 10:08pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/13 "2025-06-11T22:08:31Z")

</div>

yeah way too frequent

---

<div class="post-metadata">

**Author:** ![proteus-dev](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/proteus-dev/32/51624_2.png) [@proteus-dev](https://forum.cursor.com/u/proteus-dev)\
**Post date:** [June 12, 2025, 7:02am UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/14 "2025-06-12T07:02:37Z")

</div>

I was too quick with my judgement. but i encounter this issue:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/9/e/9e56a607c96c06e53f4ca8f3546267f51160d7f2.png)

Extension settings does not enable me to configure anything relevant in these regards as far as I can see.

maybe it got something to do with “Custom Database Path” but I am not even aware what this is. I would love to read about it but cant find information about it in the extension.

Account settings seems to be only a link to the cursor dashboard.

Any help appreciated. Should solve my problem, once I got it running.

edit: also, my problem actually does not revolve around the 500 requests, as these are always used up in a few days in my case, but my total requests per month. The /500 indicates that this is most likely only piping through this information:

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

Edit 2:  
what i am looking for is a convenient way of looking at this:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/2/5/25c91bca74f0b22331821f8055c024dde5aedaf8.png)

And this:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/5/8/58bf01a81b20c67fe259eeee87edda8d5aeb5294.png)

Edit 3:  
… and I need this for a given billing cycle; which could be a bit more confusing because cursor seems to define two different billing cycles for the 500 and the usage-based requests for reasons beyond my knowledge.

… and the next one:  
these settings indicate that the extension will provide me what I need:

 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/3/2/3248b92029ed630ca76739430e98c38d0c9f871b.png)  
 ![image](https://us1.discourse-cdn.com/cursor1/original/3X/0/3/03a956105106ec596c0b8532d871fce41c56c256.png)

Looking forward to test it.

---

<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:** [June 13, 2025, 8:51pm UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/15 "2025-06-13T20:51:51Z")

</div>

Just to add here, the team have increased the login time to 12 hours per session!

---

<div class="post-metadata">

**Author:** ![QTom](https://avatars.discourse-cdn.com/v4/letter/q/b77776/32.png) [@QTom](https://forum.cursor.com/u/QTom)\
**Post date:** [June 14, 2025, 1:08am UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/16 "2025-06-14T01:08:58Z")

</div>

Re-login every day 🤣

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [June 14, 2025, 7:49am UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/17 "2025-06-14T07:49:29Z")

</div>

It’s better than every 10 minutes, appreciate it. 🥰

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [July 14, 2025, 7:50am UTC](https://forum.cursor.com/t/dashboard-frequently-requires-re-login/102391/18 "2025-07-14T07:50:25Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
