Never lose a run. Autosave is on.

1. 1

   Timed save, every minute

   Once a minute during play, the shell writes the current game state to autosave. No button press needed — pause, close the tab, come back later.
2. 2

   Event save, on game request

   Games can request a save at natural breakpoints (e.g. after a cutscene, level clear, or day advance). Each request lands immediately, on top of the minute timer.
3. 3

   Always lands in slot 0

   Autosave writes to slot 0, the cheat-proof / cheat-free slot. Any cheat marker the client sends is stripped on write, so the autosave slot stays clean no matter what.

• Signed out: autosave keeps a device mirror so a refresh or accidental close still resumes on this device.
• Signed in: the same slot-0 write syncs to the cloud, so phone → desktop → phone resumes the same run.
• Opt-out: prefer manual saves only? Turn autosave off with the toggle in this Cloud saves section of the game shell. Timed and on-request writes stop; manual slot writes still work.

• Manual vs autosave: Save writes the manual copy; the minute-timer autosave writes the auto companion of the active slot. Autosave never overwrites your manual save.
• Active-slot rule: autosave follows the slot you are playing — the companion belongs to the active slot, not always slot 0.
• Cloud kind: ?kind=manual|auto selects which copy (omitted = both); PUT defaults to kind=manual. On this device the auto mirror lives under the :auto suffix.
• Corrupt-manual recovery: if a manual copy fails to parse or apply, Load-autosave restores the auto companion for the same slot — same run, one minute older at most.

Slot mechanics in full in Playing games · Fridge Simulator handoff in Resume anywhere.