Claude Settings Scope Diff & Merge Analyzer

What This Tool Does

Claude Settings Scope Diff & Merge Analyzer is built for deterministic developer and agent workflows.

Compare managed, user, project, and local Claude settings, resolve precedence, and inspect the final effective configuration with conflict visibility.

Use How to Use for execution steps and FAQ for constraints, policies, and edge cases.

Last updated:

This tool is provided as-is for convenience. Output should be verified before use in any production or critical context.

Agent Invocation

Best Path For Builders

Browser workflow

Runs instantly in the browser with private local processing and copy/export-ready output.

Browser Workflow

This tool is optimized for instant in-browser execution with local data handling. Run it here and copy/export the output directly.

/claude-settings-scope-diff/

For automation planning, fetch the canonical contract at /api/tool/claude-settings-scope-diff.json.

How to Use Claude Settings Scope Diff & Merge Analyzer

  1. 1

    Paste settings scopes as JSON

    Include managed, user, project, and local objects as available. Missing scopes are allowed and still produce a valid merge report.

  2. 2

    Compute effective settings

    Click Compute Effective Settings to flatten each scope and resolve precedence into one effective key-value map.

  3. 3

    Review conflicts and managed locks

    Check the conflict list and managed-locked keys to identify where local overrides are being superseded by higher-priority policy.

  4. 4

    Apply resolved values to baseline config

    Use the effective output as the canonical reference when debugging drift or preparing reproducible environment settings.

Frequently Asked Questions

What is Claude Settings Scope Diff?
Claude Settings Scope Diff compares managed, user, project, and local settings and computes the effective merged result. It highlights precedence conflicts and managed overrides in one output.
Which settings scopes are supported?
You can include any combination of managed, user, project, and local scope objects. Missing scopes are handled safely so you can still inspect effective values and conflicts.
How does the tool detect managed locks?
When the same setting key appears in managed scope and lower scopes with different values, the key is marked as managed-locked and listed in the lock summary.
Does Claude Settings Scope Diff store or send my data?
No. The diff and merge logic executes client-side and does not transmit configuration content.