A repeatedly failing policy helper now serves its configured fixed payload instead of stale output.
What's wrong with this entry?
When the periodic refresh of a policy helper keeps failing and a fixed default payload is configured, Claude Code serves that payload instead of continuing to hand out the last successful helper output.
- The switch is recorded as a
refresh_fell_back_to_defaultoutcome. - If the helper is still failing while the default is already being served, it is logged at debug level only, so repeated failures do not spam.
refresh_fell_back_to_default
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.228
Managed settings accept per-OS
policyHelpersBoth mention policy helper managed
-
v2.1.228
New
policyHelpersmanaged-settings key for per-OS policy helper executablesBoth mention policy helper managed
-
v2.1.235
Policy helpers can be delivered by remote managed settings, after explicit approval
Both mention policy helper managed