pub fn merge_values(lower: &mut Value, higher: Value)Expand description
Layers the settings document higher over lower, in place, the way
Claude Code merges settings sources (checked against 2.1.322’s
merge, a lodash mergeWith):
- Objects merge key by key, recursively: a key only one side sets
keeps its value (so
env,permissions,sandboxandhookscombine). - Arrays concatenate,
lower’s entries first, and repeated scalars are dropped (sopermissions.allow/deny/askand each hook event’s matcher groups combine). Two keys are whole values instead:fallbackModel(an ordered chain) andmodelPicker, wherehigher’s wins. extraKnownMarketplacesmerges one level deep: a marketplacehighernames replaceslower’s whole.- Anything else (scalars,
null, a type change):higherwins.
Merging decides what each key holds, not what it means: a deny rule
beats an allow rule however the layers were ordered, and Claude Code
reads some keys only from some sources (managed-only keys, keys it
ignores in project settings), which this doesn’t model.