Skip to content

fix(mcp): restart prestarted provider after config changes - #346

Merged
astyfx merged 1 commit into
mainfrom
fix/mcp-envs
Aug 7, 2026
Merged

fix(mcp): restart prestarted provider after config changes#346
astyfx merged 1 commit into
mainfrom
fix/mcp-envs

Conversation

@astyfx

@astyfx astyfx commented Aug 7, 2026

Copy link
Copy Markdown
Member

Summary

  • Ensure MCP configuration edits made after provider startup take effect on the first turn.
  • Prevent a prestarted process from using a stale native configuration snapshot.

Changes

  • Track provider process startup time and pass it into MCP refresh checks.
  • Compare configuration modification times against process startup during the initial fingerprint check.
  • Restart the provider when configuration changed after startup but before the first turn.
  • Add regression coverage for initial refresh detection and the prestarted-process lifecycle.

@astyfx
astyfx requested a review from a team as a code owner August 7, 2026 06:32
@astyfx
astyfx requested review from JongSikLim and heath-s and removed request for a team August 7, 2026 06:32
@astyfx
astyfx enabled auto-merge (squash) August 7, 2026 06:32

@heath-s heath-s left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved

@astyfx
astyfx merged commit f853f28 into main Aug 7, 2026
3 checks passed
@astyfx
astyfx deleted the fix/mcp-envs branch August 7, 2026 06:32
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.

2 participants