{"version":"2.1.225","anchor":"daemon-auth-cooldown-and-status-can-go-through-the-v5-storag","canonical_anchor":"daemon-auth-cooldown-and-status-can-go-through-the-v5-storag","heading":"Daemon auth cooldown and status can go through the v5 storage layer","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/daemon-auth-cooldown-and-status-can-go-through-the-v5-storag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Daemon auth cooldown and status can go through the v5 storage layer\n\nBackground daemon login cooldown and status can live in a storage service instead of local files.\n\n**What**\n\nThe headless daemon's browser-login cooldown and auth-status records can now be read and written through the v5 storage client instead of files in the config dir.\n\n**Details**\n\n- both records gained state keys for the v5 layer\n- active only when the supervisor is constructed with a storageV5 client\n- dedicated failure reporting on that path, for example `daemon-auth v5 cooldown read failed`\n- falls back to the `daemon-auth-cooldown` and `daemon-auth-status.json` files under the config dir when no client is passed\n\n**Evidence**\n\n`daemon-auth-cooldown`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}