merge-settings

To merge Claude project settings, you consolidate permissions from project-local .claude/settings.local.json files into the global ~/.claude/settings.json file. This process identifies new rules, proposes them for approval, and writes deduplicated, canonicalized JSON to the global config.

You need to consolidate per-project Claude permission rules when managing multiple Claude projects and want centralized configuration control. It extracts permissions.allow entries from local project files, compares them against global settings, and proposes safe, deduplicated rules for explicit approval before merging.

Yes, you can back up global Claude settings before applying new permissions. The merge process automatically backs up the existing global ~/.claude/settings.json file before proposing and merging any approved permission rules, ensuring your previous configuration is safely preserved.

Yes, the Claude settings merge process requires explicit user approval. After computing the diff between local and global settings, it proposes new or updated rules and only updates the global config with canonicalized JSON after you explicitly approve the proposed changes.

Yes, you need jq installed to merge local Claude settings into global config. The merge process relies on the jq dependency to read both local and global settings files, compute diffs between permission rules, and write the final canonicalized JSON output.

The best way to manage multiple Claude projects with different permission rules is merging project-local settings into a centralized global config. This approach extracts local permissions, deduplicates overlapping rules, and requires explicit approval before applying canonicalized updates to the global file.