Hi, while it is true you can only use Cursor on one machine at a time at once, we totally want to support use cases where you may have multiple machines, and want to use Cursor on one at a time!
We think this issue occurred due to some changes we made that have had unintended side effects, but we should be resolving this in the next 24 hours!
Maybe you use two devices simultaneously right, I also use two devices, one at my work and one at home and never faced the same issue, many people share account so I think that policy is understandable to prevent our pro users from being abused
After verification, I found that this phenomenon is related to the client version. From 0.48.8 to 0.48.9, one client login will activate more than 10 sessions, which leads to the expiration of previous sessions
If 0.48.7, this will not happen, and logging in once will only activate one session
This has nothing to do with sharing sessions. When a computer opens two cursor windows, versions 0.48.8~0.48.9 can only keep one window’s login valid. When you open both front-end and back-end projects at the same time, this is a disaster. When the front-end project is in use, the back-end project’s session will be logged out, which is completely incomprehensible
Based on this, it should be 0.48.8~0.48.9 client, which activated multiple sessions abnormally and caused automatic logout
0.48.7 currently appears normal, 0.48.9 is definitely abnormal, and 0.48.8 is not very certain