{"version":"2.1.281","anchor":"bootstrap-config-new-flat-v1-json-schema-and-per-value-ve","canonical_anchor":"bootstrap-config-new-flat-v1-json-schema-and-per-value-ve","heading":"Bootstrap config: new flat (v1) JSON schema and per-value version stamps","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/bootstrap-config-new-flat-v1-json-schema-and-per-value-ve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Bootstrap config: new flat (v1) JSON schema and per-value version stamps\n\nThe shared bootstrap configuration gains a flat (v1) format, and each setting is now tagged with the first Desktop release that reads it\n\n**Unclear.** The finding does not say whether anything in Claude Code already sends or reads the flat v1 format.\n\n**What**\n\nBootstrap configuration is the per-user setup information handed to the app when it starts. The code that describes its format adds a second, flat version called `bootstrap-config-v1`, built by `buildFlatBootstrapJsonSchema`.\n\nEach setting, and some of the individual choices a setting allows, is now tagged with the first Desktop release that understands it. Examples include the `mantle` choice for inferenceProvider and the `workforce` and `oauth` choices for credential kind. The rules for overriding `models` per group moved into a separate part of the code.\n\n**Why**\n\nThe version tags record which Desktop releases can read a given setting or choice, so a configuration using a newer choice can be matched against the app versions that support it."}