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.

1. 1

   Finish on the phone, signed in

   Play while signed in so the slot writes sync to the cloud, and note which slot number you are on. Signed-out play keeps only the device mirror, which never leaves that browser.
2. 2

   Open the same game on desktop

   Sign in with the same account on the second device (check /account if you are unsure which account holds the run) and open the same game.
3. 3

   Load the same slot and kind

   Pick the same slot 0 to 3 you played on the phone. Load the manual copy for your save, or the auto companion if the manual copy ever fails: same run, at most a minute older.

• 🧭 Run did not follow me. The usual causes, in order: one device was signed out, the two devices use different accounts, or a different slot was loaded. Fix: sign in on both, confirm the same account, load the same slot number.
• 🧩 Manual load fails. Load the auto companion of the same slot instead. If the manual copy fails to parse, the companion restores the same run from at most a minute earlier.
• 🖋️ Slot shows a cheat mark. That mark is permanent and survives delete and recreate. Move the serious run to cheat-proof slot 0 and keep the branded slot for chaos.
• 👻 Guest progress vanished. The device mirror lives in that browser only: clearing site data, switching browsers, or switching devices ends it. Sign in for cloud slots that travel.
• ⏸️ Autosave stopped writing. Check the opt-out toggle in the Cloud saves section of the game shell. Timed and on-request writes stop while it is off; manual slot writes still work.

• 🗄️ Slot. One of four numbered homes (0 to 3) per game. Each slot holds two copies: manual plus auto.
• ✍️ Manual copy. The write your Save button makes. Loads with Save plus Load; never touched by the minute timer.
• 🤖 Auto companion. The Load-only backup the timer refreshes. Restores the same slot when the manual copy fails.
• 🔀 Kind. The cloud selector: ?kind=manual fetches your save, ?kind=auto fetches the companion, omitting it fetches both.
• 📱 Device mirror. The signed-out browser copy, with the auto mirror stored under the :auto suffix. Handy, but homebound.
• 🖋️ Cheat mark. The permanent cheat_mode:true brand on slots 1 to 3 once cheats are used. A database invariant, not a label.

• 👁️ Glance at the slot number. Confirm you are writing to the slot you mean: 0 for the keeper run, 3 for the chaos run. A save in the wrong slot is not lost, just parked where you will not look.
• 👤 Glance at the login. If the header offers Login instead of Dashboard, this browser holds only a mirror. Sign in before the milestone moment, not after it.
• 💾 Press Save on milestones. Autosave covers minutes, not meaning: after a boss, a cutscene, or a perfect day, write the manual copy deliberately so the companion is never your only witness.
• 🧾 Verify on the next visit. When you return, load the slot and confirm the run before playing on. Catching a wrong slot early costs seconds; catching it after an hour of overwriting costs the hour.

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