{"version":"2.1.318","anchor":"design-consent-delete-treats-404-as-removed","canonical_anchor":"design-consent-delete-treats-404-as-removed","heading":"Withdrawing design consent clears it locally even if the server already removed it","tier":"notice","area":"Design Consent","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/design-consent-delete-treats-404-as-removed","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Withdrawing design consent clears it locally even if the server already removed it\n\nIf the server says your design consent is already gone, Claude Code now clears it locally too but still shows an error\n\n**What**\n\nWhen you withdraw design consent, Claude Code asks the server to delete it. If the server answers that there was nothing to delete (a \"not found\" response), Claude Code now clears its own record of your consent and still reports an error. Before, a \"not found\" answer counted as a success. Now any response that is not a success counts as an error.\n\n**Why**\n\nYour local consent state no longer stays out of step with the server when the server has already removed the consent. You may see an error in that case even though the consent is gone.\n\n- Area: Design Consent\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}