# 2026-04-18 — Session Notes## CasaOS Shutdown Preparation- Topher requested all agents save to memory before CasaOS shutdown- Sent save-to-memory notices to: psb-gemma ✅, psb-business (timeout), 2890-bot (timeout), crash-bot (timeout), crash-bot-public (timeout)- Gemma confirmed: "Saved. Going down with the ship. 👋"- Timeouts likely mean those sessions were idle — their memory files are already on disk## Crash-Bot Model Override Fix- crash-bot was stuck on `minimax-m2.7` instead of `glm-5.1:cloud`- Root cause: `sessions.json` had sticky `modelOverride: minimax-m2.7` on `agent:crash-bot:main` and `agent:crash-bot:discord:direct:266336985692635139`- The Discord channel session was fine (no override, already on glm-5.1:cloud)- Fixed by clearing modelOverride and resetting model to `glm-5.1:cloud` in sessions.json- Verified GLM-5.1 cloud API is working (direct curl test returned valid response)- Crash-bot's own memory noted: "Session started with minimax-m2.7 — not default glm-5.1:cloud. Cause unknown."## End of Day Summary (Apr 18)- System stable — ~5 days uptime- Dreaming: fired Apr 17 at 03:16 and 11:34 UTC, but NOT today (Apr 18)- Both days: events.jsonl + short-term-recall.json written to memory/.dreams/ (DREAMS.md still NOT written — persistent bug)- No user interaction today- P102-100 GPU: still not detected, Quadro K600 only