Problem: Multiple tools write ~/.claude.json - do they conflict when installed together? (measured compatible) —— Trove problem library

What you will run into

You want to install agt, deepcode, and code-review-graph together; they all write ~/.claude.json at install time (MCP/plugin registration sections), and you worry they'll overwrite each other, breaking a tool or losing config. Measured conclusion: they can be installed together - no conflict.

Why this happens

All three write ~/.claude.json, but each writes a different key/section:

JSON merges by key; measured coexistence keeps the structure intact with no overwrites. claude-mem uses its own write surface ~/.claude-mem/ and is measured compatible with all three.

~/.claude.json is a shared write surface across tools, but its merge semantics are "merge by key":

each tool writes its own section (agt writes policy/governance keys, deepcode and code-review-graph write their own MCP/tool-registration keys), and each reads only its own keys — object-level JSON merging does not overwrite unless two tools write the same key.

Deterministic takeaway: safety of a shared write surface depends on "whether the key spaces are isolated", not "whether it is the same file"; the verified intact coexistence of the three tools means their key spaces are disjoint;

to judge a new tool, check which keys it writes in ~/.claude.json and compare with existing ones;

claude-mem uses a separate directory ~/.claude-mem/ (a different write surface), naturally isolated from the shared-surface writers — write-surface analysis is far more accurate than the "same file = conflict" intuition.

Step by step

1. Install each with its official command — Required

agt, deepcode, code-review-graph, and claude-mem coexist in the same environment; no forced order.

2. Verify after installing — Required

python3 -m json.tool ~/.claude.json

Must parse; then smoke-test each tool (agt lint-policy / crg build / deepcode diagnostic command) - all exit 0 means normal.

3. Re-smoke after upgrades — Required

Re-run smoke tests after upgrading any tool; if config looks wrong, back up ~/.claude.json first, then investigate (站内冲突预检说明 shows write-surface conflicts first).

How to confirm it works

All smoke tests green (measured shape):

agt lint-policy -> exit 0
crg build -> exit 0
deepcode diagnostic command -> exit 0
python3 -m json.tool ~/.claude.json -> parses

Other environments

Symptom

You want to install agt, deepcode, and code-review-graph together; they all write ~/.claude.json (MCP/plugin registration sections), and you worry they'll overwrite each other, breaking a tool or losing config.

Cause

All three write ~/.claude.json but write different key/sections: agt writes the policy/governance section, deepcode and code-review-graph write their own MCP/tool registration sections; JSON merges by key, measured coexistence keeps the structure intact with no overwrites. claude-mem uses its own write surface ~/.claude-mem/ and is measured compatible with all three.

Solution

1. Install each with its official command (agt, deepcode, code-review-graph, claude-mem coexist in the same environment).
2. Verify after installing: python3 -m json.tool ~/.claude.json must parse; then smoke-test each tool (agt lint-policy / crg build / deepcode diagnostic command) - all exit 0 means normal.
3. Re-smoke after upgrading any tool; if config shows anomalies, back up ~/.claude.json first, then investigate (the marketplace precheck 站内冲突预检说明 shows write-surface conflicts first).