You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Managed settings fetch fails on every launch: "model: Expected string, received object" (v1.0.105, macOS) #5342
On a managed (enterprise) account, the CLI constantly shows: Managed account policy could not be refreshed: the managed-settings fetch failed. Retrying automatically. Running /login clears it only in that terminal; every new terminal shows it again.
Log evidence (~/.copilot/logs)
[WARNING] [managedSettings] server policy fetch failed — no cache to fall back on, failing open: [fetchManagedSettings] Unexpected response format: model: Expected string, received object
It repeats roughly every 30s. No MDM policy is present on the device. The policy is never cached, so the retry loop never ends.
Expected
The managed-settings response is parsed (the model field accepts the object shape the server returns), the policy is cached, and the warning stops.
Environment
Copilot CLI 1.0.105 (latest per copilot update)
macOS (Apple Silicon)
Auth: GitHub.com managed/enterprise account
SSL_CERT_FILE and NODE_EXTRA_CA_CERTS are set (corporate CA); this only adds unrelated forceLoginOrgs warnings
Impact
Fail-open, so the CLI keeps working, but the warning is constant and bypass-permissions mode is disabled.
Same on Windows 11 (v1.0.105, winget, forerunner build), but a different field fails validation:
[fetchManagedSettings] Unexpected response format: fusionTier: Invalid enum value. Expected 'standard' | 'high' | 'max' | 'unmanaged', received 'Standard'
Looks like the server response schema changed and the 1.0.105 client wasn’t updated to match.
Activity
gxv383 commentedon Nov 3, 2026
Same on Windows 11 (v1.0.105, winget, forerunner build), but a different field fails validation:
[fetchManagedSettings] Unexpected response format: fusionTier: Invalid enum value. Expected 'standard' | 'high' | 'max' | 'unmanaged', received 'Standard'
Looks like the server response schema changed and the 1.0.105 client wasn’t updated to match.