{"version":"2.1.293","anchor":"cowork3p-config-schema-additions","canonical_anchor":"cowork3p-config-schema-additions","heading":"New admin setting keeps less Claude Desktop configuration cached on disk","tier":"use","area":"Desktop App","scope":"org","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/cowork3p-config-schema-additions","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### New admin setting keeps less Claude Desktop configuration cached on disk\n\nA new `disableLocalConfigCache` admin setting keeps only the organization ID and restrictions on disk, alongside other Claude Desktop policy changes\n\n**What**\n\nThese are admin policy settings for Claude Desktop that ship as part of Claude Code. An admin policy is configuration an organization sets for everyone who uses the app. The changes:\n\n- `disableLocalConfigCache` is a new setting that keeps only the organization ID and its restrictions stored on the computer.\n\n- The list of allowed outbound hosts now says that any list other than `*` also limits where Claude may browse in the built-in browser.\n\n- Many settings are now marked as applying to the desktop app.\n\n- `redirectHost` appears as a new setting name.\n\n- Configuration applied while the app is running now follows a rule that needs two checks in a row.\n\n**Why**\n\nOrganizations that manage Claude Desktop can keep less of their configuration stored on each machine. The browsing note makes clear that limiting outbound hosts also limits the built-in browser.\n\n- Area: Desktop App\n- Tier: Use it now\n- Useful: 3\/5\n- Signal: 2\/5\n- Scope: org\n- Heads-up: no"}