Start · 5 min read
Accounts and sign-in sessions
Understand persistent sign-in, background renewal, explicit logout, plans, and recovery.
On this page
Sign-in persists across restarts
Gyroscape stores the desktop account session securely on the device and renews short-lived service access in the background. Expired access should trigger one refresh and retry, not remove the account or return you to login.
Task history remains available after restarting. A temporary network or service interruption can pause a request, but it is not an intentional logout.
Log out when you choose
Open the account menu in the lower-left corner and choose Log out. Logging out ends the device session but does not delete project folders or source-control history.
A new sign-in can be required if the account is disabled, access is revoked, or the stored security credential becomes invalid. Those are authorization changes, not idle-time expiration.
Plans, usage, and models
Account controls show the current plan and upgrade path when available. Model access, effort levels, and usage limits can differ by plan and deployment. The model picker is the current source of truth.
Reaching a usage limit does not erase the session. Continue after access is restored or select another available option.
Unexpected login screen
Check the network, reopen the app, and sign in once if prompted. If requests repeatedly return 401 while the account still appears signed in, record the time, model, and visible error before contacting support. Do not repeatedly clear application data because that can remove useful diagnostics.
Related articles