Skip to main content

merge_values

Function merge_values 

Source
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, sandbox and hooks combine).
  • Arrays concatenate, lower’s entries first, and repeated scalars are dropped (so permissions.allow/deny/ask and each hook event’s matcher groups combine). Two keys are whole values instead: fallbackModel (an ordered chain) and modelPicker, where higher’s wins.
  • extraKnownMarketplaces merges one level deep: a marketplace higher names replaces lower’s whole.
  • Anything else (scalars, null, a type change): higher wins.

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.