{"version":"2.1.300","anchor":"config-schema-claude-code-reader-and-quickwriteenabled-key","canonical_anchor":"config-schema-claude-code-reader-and-quickwriteenabled-key","heading":"Shared config schema adds a 'code' reader for Claude Code, not yet served, plus a quickWriteEnabled setting","tier":"soon","area":"Managed Settings","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/config-schema-claude-code-reader-and-quickwriteenabled-key","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### Shared config schema adds a 'code' reader for Claude Code, not yet served, plus a quickWriteEnabled setting\n\nThe organization config schema now lists Claude Code as a third reader, marked not served, and adds a quickWriteEnabled setting\n\n**What**\n\nAn organization can manage settings centrally through a shared config schema. That schema lists the apps that read those settings, called readers. Before, there were two: `desktop` and `m365`. A third reader, `code`, is now listed. It stands for the Claude Code CLI signed in to the organization by itself. Its entry is marked:\n\n- `served: false`\n\n- `readsBootstrap: false`\n\n- `inExternalBuild: true`\n\nThe same schema change also adds:\n\n- A `quickWriteEnabled` setting, labelled \"Allow Quick Write\". It is first-party scoped and public but undocumented.\n\n- An `exportTemplate` on the organization-sharing field.\n\n- A new helper and a new `offDeviceExecutionTargets` export.\n\n**Why**\n\nNothing in this schema says Claude Code reads these organization settings yet, and the `code` reader is explicitly marked as not served. In practice, settings an organization manages this way do not reach Claude Code in this release.\n\n- Area: Managed Settings\n- Tier: Nothing to try yet\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: org\n- Heads-up: no\n- Present in the build but not switched on"}