{"version":"2.1.304","anchor":"grove-settings-response-validated","canonical_anchor":"grove-settings-response-validated","heading":"Malformed Grove settings from the server now count as a failed fetch","tier":"internal","area":"Privacy Settings","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/grove-settings-response-validated","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Malformed Grove settings from the server now count as a failed fetch\n\nWhen Claude Code fetches Grove settings, an answer whose `grove_enabled` value is not true, false or empty is now treated as a failure\n\n**What**\n\nWhen Claude Code fetches its Grove settings from the server, it now checks the `grove_enabled` value in the answer. If that value is not true, false or empty, the fetch fails with an error.\n\n**Why**\n\nA malformed answer from the server is now handled as a failed fetch instead of being used as if it were valid.\n\n- Area: Privacy Settings\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}