Problem: "My config got changed" after install / suspected conflict with omc, agt —— Trove problem library

What you will run into

After running code-review-graph install (or init), you find ~/.claude.json, ~/.codex/hooks.json etc. have been written to; if you also installed oh-my-claudecode and agent-governance-toolkit, you start suspecting they're fighting each other.

Your first reaction is "infected/bug", but this is actually the tool's normal behavior.

Why this happens

The install subcommand registers MCP/hooks with the detected AI platforms - that's its designed functionality, not a fault:

It shares file-level write surfaces with omc/agt (different keys/sections), judged possible-conflict (co-install not measured; won't claim measured state). All writes can be fully cleaned by the official code-review-graph uninstall.

An AI tool's "install" is essentially registration: writing MCP/hooks registration sections into each client's shared config files so the client can discover and load the tool at startup.

install performs exactly those writes, so "config changed after install" is not an anomaly — it's the definition of installation.

Two deterministic conclusions follow: first, write surfaces are public contract — which files and sections get written is documented in the guide/manifest, so reading the write-surface list before installing keeps you calm;

second, same-file write surface ≠ conflict — omc/agt and crg write the same set of files but different keys/sections, just like two programs each writing their own config items;

only writing the same key can overwrite each other (that's a real conflict). The judgement is standardized: check whether the conflict matrix says possible-conflict or measured conflict, don't guess.

The rollback path is also fixed: the official uninstall is the inverse of those writes and fully revokes the registration.

Step by step

1. Know the write surfaces before installing — Required

install registering MCP is a feature, not a fault. Knowing it will write these files beforehand keeps you calm.

2. Co-install strategy — Required

With omc/agt in the same environment: install one, get it working, then evaluate the next. Conflict semantics in site docs (possible-conflict; no measurement, no claiming measured state).

3. Clean leftovers — Required

After the official uninstall, manually confirm the checklist:

ls -la ~/.claude.json ~/.codex/hooks.json ~/.cursor/mcp.json 2>/dev/null && ls -la .code-review-graph/

Confirm the workspace .code-review-graph/ and the matching sections in each config file are gone.

How to confirm it works

After uninstall, the config files no longer contain code-review-graph sections (expected output shape):

grep -c code-review-graph ~/.claude.json
-> 0 (or no such section)

The mcpServers/hooks in each AI platform config are back to normal; other tools unaffected.

Other environments

Symptom

After running code-review-graph install (or init), ~/.claude.json, ~/.codex/hooks.json etc. are written; or when co-installed with oh-my-claudecode and agent-governance-toolkit, you suspect interference.

Cause

The install subcommand registers MCP/hooks with the detected AI platforms: ~/.claude.json (mcpServers), ~/.codex/hooks.json, ~/.cursor/mcp.json, ~/.config/opencode/plugins/crg-plugin.ts, workspace .claude/settings.json and .mcp.json - normal behavior of this tool (multi-registration surfaces). Same-file write surfaces with omc/agt (different keys/sections), judged possible-conflict (co-install not measured).

Solution

1. Know the write surfaces before installing: install registering MCP is a feature, not a fault; everything can be fully cleaned by the official code-review-graph uninstall.
2. Co-install strategy: with omc/agt in the same environment, install one and get it working before evaluating the next; conflict semantics in site docs (possible-conflict; no measurement, no claiming measured state).
3. Clean leftovers: official uninstall + manual checklist (workspace .code-review-graph/, ~/.claude.json mcpServers section, ~/.codex/hooks.json, ~/.cursor/mcp.json).