You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Tests: isolate HOME so user-global MCP config cannot leak into test runs #1682
MCP discovery reads ~/.claude.json and other home-level config from the real home directory, so tests fail on developer machines that have MCP servers configured.
The linked issues hold the original reports and reproductions. Most are closed in favor of this tracker; any child with an open fix PR stays open until that PR lands.
Hi @anandgupta42, I'd like to take this. Plan: point HOME (and the other home-config lookups) at a temp dir in the shared test setup so MCP discovery never reads the real ~/.claude.json, keep #1024's status test as a regression case, and add a test that a populated real home doesn't leak in. Okay to go ahead?
Activity
rahulsjha commentedon Nov 21, 2026
Hi @anandgupta42, I'd like to take this. Plan: point HOME (and the other home-config lookups) at a temp dir in the shared test setup so MCP discovery never reads the real
~/.claude.json, keep #1024's status test as a regression case, and add a test that a populated real home doesn't leak in. Okay to go ahead?