Release2026-10-13

GitHub added a setting to force Copilot clients to refresh managed settings at startup. The setting is `forceRemoteSettingsRefresh` and can be set to `true`. It works in Copilot CLI, VS Code, and the GitHub Copilot app. MDM and file-based delivery can require freshness before first sign-in. Server-managed values require refreshes on subsequent startups after first receipt. Clients fail closed if they cannot confirm current policy. Without the setting, clients use the normal cache. GitHub also added minimum client version enforcement to the `sandbox` key. Users on older versions must update to use Copilot.

What changed

Clients used cached managed settings for faster startup and resilience during failures.

What it unlocks

Forcing clients to fetch current server-managed settings before Copilot starts.

What you need to act on it

  • server-managed, MDM-managed, or file-based settings
  • supported GitHub Copilot clients (CLI, VS Code, GitHub Copilot app)
  • minimum client version for `sandbox` key

Sources

Send this to someone who needs it

Shares the story and its sources. Nothing about you.

What does this mean for your job?

This is the story as everyone gets it. Once a week we send you the version written for your role — what changed, why it matters for the work you actually do, and one thing to try. Free while we tune it.