LMOS VOID Beta 0.34.1: Session Continuity and the Road to 1.0
LMOS now treats desktop continuity as a release requirement: open windows survive normal browser returns, legacy window state migrates forward, and users can deliberately start with a fresh desktop. The beta-to-1.0 program now also formalizes ChatGPT as the architecture/QA direction layer and Floot as the execution platform.
What changed
Desktop window state now persists beyond a single browser-tab session so returning users can continue where they left off.
Existing v1/v2 session records still migrate into the current window state model.
Window restore data expires after a bounded period rather than living forever.
Signing out clears persisted desktop state.
The Window menu now includes Start fresh desktop for users who want a clean workspace immediately.
The beta-to-1.0 operating plan now treats session continuity, recovery, critical journeys, permissions, backups, accessibility, security and release gates as requirements rather than polish.
ChatGPT is the primary architecture and QA direction layer; Floot is the execution/platform layer; Floot AI remains reserved for intentional in-product AI with entitlement and cost controls.
Why this matters
An operating system earns trust by remembering context without trapping the user in it. The goal for Genesis 1.0 is not to look finished; it is to behave predictably enough that creators trust where their work is, whether it is saved, how to recover it and what happens next.
What testers should try
Open several LMOS windows, close the browser normally, return later and confirm the workspace restores.
Minimize or maximize a window before leaving and confirm the state remains coherent on return.
Choose Window → Start fresh desktop and confirm restored windows are cleared without deleting projects or files.
Sign out and confirm the old desktop session does not reappear for the next account.
Use the beta on real work.
The most useful feedback is not “I like it.” Tell us where you hesitated, what took too many clicks, what did not save the way you expected, and what would make this useful enough to return to next week.