Skip to content

fix(desktop): honour CLAUDE_CONFIG_DIR in agent MCP config panel - #3600

Open
Chessing234 wants to merge 1 commit into
block:mainfrom
Chessing234:fix/claude-config-dir-mcp-panel
Open

fix(desktop): honour CLAUDE_CONFIG_DIR in agent MCP config panel#3600
Chessing234 wants to merge 1 commit into
block:mainfrom
Chessing234:fix/claude-config-dir-mcp-panel

Conversation

@Chessing234

Copy link
Copy Markdown
Contributor

Summary

  • Resolve Claude settings + MCP config from the agent’s CLAUDE_CONFIG_DIR when set
  • Default remains ~/.claude/settings.json + ~/.claude.json
  • Panel “From config file (…)” attribution points at the isolated .claude.json

Why

Isolated Claude agents correctly load an empty MCP set at runtime, but the config panel always listed the operator’s ~/.claude.json servers and labeled them enabled (#3493).

Test plan

  • Agent with CLAUDE_CONFIG_DIR=<nest>/claude-config and empty .claude.json — panel MCP list is empty and path shows the nest dir
  • Agent without the env var — panel still shows ~/.claude.json
  • Unit tests for isolated vs default path resolution

Fixes #3493

Made with Cursor

The config bridge always read ~/.claude.json, so isolated agents still
showed the operator's MCP servers. Resolve settings and MCP paths from
the agent's CLAUDE_CONFIG_DIR when set.

Signed-off-by: Taksh <takshkothari09@gmail.com>
@Chessing234
Chessing234 requested a review from a team as a code owner July 29, 2026 18:40
@Chessing234

Copy link
Copy Markdown
Contributor Author

@tlongwell-block @wesbillman @wpfleger96 mind taking a look when you get a chance?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Agent config panel lists MCP servers from hardcoded ~/.claude.json, ignoring per-agent CLAUDE_CONFIG_DIR

1 participant