Skip to content

fix(core): reload changed MCP config - #41204

Merged
rekram1-node merged 1 commit into
v2from
mcp-config-reload
Aug 8, 2026
Merged

fix(core): reload changed MCP config#41204
rekram1-node merged 1 commit into
v2from
mcp-config-reload

Conversation

@opencode-agent

@opencode-agent opencode-agent Bot commented Aug 8, 2026

Copy link
Copy Markdown
Contributor

Summary

  • subscribe each location-scoped MCP service to config.updated
  • compare the previous and next effective MCP server maps before reconciling
  • add, replace, or remove only server entries whose effective configuration changed
  • preserve API-registered servers that are not owned by config updates
  • reconcile once after installing the live subscription so startup-time config changes cannot be lost

Strict reconciliation behavior

Unrelated config edits and semantically unchanged MCP entries do not restart existing MCP connections. Effective server changes—including inherited MCP timeout changes—replace only the affected server. Added and removed config entries affect only their corresponding names.

Verification

  • bun test test/mcp.test.ts in packages/core (24 passed)
  • bun typecheck in packages/core
  • scoped oxlint on the changed implementation and test files (no errors; existing warnings only)

Requested by: @rekram1-node (Aiden Cline via Slack)

@opencode-agent
opencode-agent Bot force-pushed the mcp-config-reload branch from 7931425 to d93aa33 Compare August 8, 2026 04:43
@rekram1-node
rekram1-node merged commit bc93da4 into v2 Aug 8, 2026
6 of 8 checks passed
@rekram1-node
rekram1-node deleted the mcp-config-reload branch August 8, 2026 04:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant