I noticed that refreshing the Veras web app sometimes asks the user to log in again. This can interrupt the workflow, especially when reviewing renders, navigating the gallery, or returning to the app after a short break.
It seems like the login session may not always be preserved correctly after a page reload. The app may be losing track of the active user session, the session token may not be retained properly, or the session may be expiring sooner than expected.
When this happens, the user also loses the current workspace and the renders from that active session, even though those renders are still available later in the gallery. The user essentially has to start a fresh session, which makes the workflow feel less seamless during regular use.
Thanks for the detailed report — this is real, though it isn’t the token expiring early. Veras Web deliberately keeps the Chaos token in memory only (never in localStorage or a cookie), so a full page reload drops it, and app state lives in memory too, which is why the workspace resets; completed renders are stored server-side, hence still in your gallery. It feels intermittent because of where you’re running: inside a host app (Revit, Rhino, SketchUp, Forma) the host re-sends its login at startup so a reload re-authenticates silently, while in the standalone browser there’s no such source — though if your Chaos SSO cookie is still valid, clicking Log In bounces straight through without credentials. Licensing seats aren’t affected — the session is released on unload, and any orphan expires after ten minutes.
The fix: login is moving to a modal that opens on top of the running app rather than replacing it. Re-authenticating after an expired token or a dropped connection will happen in place, with your workspace and in-progress work intact behind the modal.