Repository navigation
agentmeld 0.1.1
uv tool install agentmeldFixed — data loss when adopting shared config
0.1.0 treated any JSON file matching an adapter target as ours to move, so .gemini/settings.json — which holds all of Gemini's settings, not just MCP — was moved wholesale into .ai/mcp.json. Real settings would vanish from where Gemini reads them. .vscode/mcp.json and its inputs key were affected the same way.
Merged targets are now adopted by copying out only our servers, leaving your file in place. Vendor-shape keys (type: stdio, source: custom) are stripped so canonical form stays neutral.
If you ran 0.1.0, check .gemini/settings.json and .vscode/mcp.json are intact. Originals are in .ai/.backup/.
Added — agentmeld restore
A supported way back out. agentmeld restore turns every mirror into a real file and stops managing the repo, leaving every tool working. agentmeld restore --from-backup puts your pre-init files back byte for byte. Both accept --dry-run.
Also
- adoption now respects the
unverifiedconfidence gate that syncing already respected - errors name the offending file instead of a bare
Expecting value: line 1 column 1 - comments in an existing JSONC
.vscode/mcp.jsonare reported when a rewrite drops them, rather than disappearing silently restorematches hook commands exactly, instead of deleting any hook containing the string "agentmeld"--rootis accepted both before and after the subcommand