{"version":"2.1.269","anchor":"userwritable-flag-added-to-managed-settings-parse-error","canonical_anchor":"userwritable-flag-added-to-managed-settings-parse-error","heading":"userWritable flag added to managed-settings parse-error","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269\/e\/userwritable-flag-added-to-managed-settings-parse-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.269","markdown":"### userWritable flag added to managed-settings parse-error\n\nManaged-settings parse errors now report whether the file is user-writable\n\n**Unclear.** What consumes this new field, or whether it changes any user-facing error message, is not stated.\n\n**What**\n\nWhen a managed settings document fails to parse as valid JSON, the diagnostic information Claude Code produces now includes a `userWritable: true` field, in addition to whatever it already reported.\n\n**Why**\n\nKnowing whether the broken settings file is writable by the current user likely helps decide whether Claude Code (or the user) can fix the parse error directly, versus needing elevated permissions or admin intervention.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}