Skip to content

Conversation

@1code-async
Copy link
Contributor

@1code-async 1code-async bot commented Jan 29, 2026

Summary

  • Watches ~/.claude.json for changes using chokidar (same pattern as git watcher) and automatically clears MCP caches + notifies renderer
  • When config changes are detected, the renderer invalidates getAllMcpConfig and getMcpConfig tRPC queries so the settings UI and MCP indicator refresh automatically
  • The next chat message in any tab will use the updated MCP server configuration without requiring a restart

Fixes ENG-590: Users no longer need to manually re-initialize MCP servers after editing their Claude config.

Test plan

  • Edit ~/.claude.json to add/remove an MCP server while the app is running
  • Verify the MCP settings tab (getAllMcpConfig) auto-refreshes to show the new config
  • Verify the MCP indicator in the chat UI reflects changes after sending a new message
  • Verify no issues on app startup/shutdown (watcher init/cleanup)
  • Verify rapid config edits are debounced properly (300ms)

🤖 Generated with Claude Code

Watch ~/.claude.json for changes using chokidar and automatically
re-initialize MCP servers in the active tab. Previously, users had
to manually restart the app or refresh when editing their Claude
config (e.g., adding MCP servers).

When a config change is detected:
1. Main process clears MCP config and working servers caches
2. IPC event notifies all renderer windows
3. Renderer invalidates tRPC queries to refetch MCP config
4. Next chat message uses the updated MCP server configuration

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
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.

0 participants