{"version":"2.1.281","anchor":"desktop-managed-config-schema-new-ask-session-tool-policy","canonical_anchor":"desktop-managed-config-schema-new-ask-session-tool-policy","heading":"Desktop managed-config schema: new 'ask-session' tool policy and version-support tags","tier":"internal","area":"Managed Settings","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/desktop-managed-config-schema-new-ask-session-tool-policy","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Desktop managed-config schema: new 'ask-session' tool policy and version-support tags\n\nThe desktop managed-config schema now tags `ask-session` and several other settings with the app version that supports them\n\n**Unclear.** The finding does not say what `SSH_CLIENT_UNREADABLE_STAND_IN` is used for.\n\n**What**\n\nThe settings schema describes which managed settings an organization can set for the desktop app. It now records the minimum app version for several of them:\n\n- `ask-session` tool policy value: from `1.21459.0`.\n\n- \"Helper cache TTL (sec)\": from `1.21459.0`.\n\n- \"Default for tier\": from `1.13576.0`.\n\n- `broker` value for `inferenceFoundryAuthFlow`: from `1.24012.0`.\n\n- The headers-helper refresh buffer and `additionalRedirectReferrerHosts`: now carry version gates too.\n\nA constant `SSH_CLIENT_UNREADABLE_STAND_IN` with the value `\"\/dev\/null\/unreadable-ssh-client\"` is also added.\n\n**Why**\n\nAdmins can see which app version is needed before a setting or value takes effect, so a policy is not set for a version that cannot use it.\n\n- Area: Managed Settings\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}