Auto-reload lived only in the dev host process, so every restart reset it to off and re-enabling it cost a confirmation dialog each session. The setting now persists to settings.json in the development data directory (same atomic write pattern as connections.json) and is restored — and re-armed — at startup.