Repository navigation
Conversation
…, repeated reload and collisions
…on isolated fixtures
Contributor
Author
|
Follow-up operator validation (2026-11-21), incorporated into the PR description and docs:
This is an operator's installed-service smoke test, not a claim of binary identity with this PR's current head. Prior feature-code CI was green; the latest docs-only head should be independently checked by CI before merge. |
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this adds
Codexify can reload one already-configured MCP source using
reload_mcp({source}), without restarting the main service, existing ChatGPT tunnel/sessions, or unrelated MCP sources. This is a transactional replacement, not an unrestricted process launcher.Implementation
Verification
8c305401150f9641d4db7ffc32e1c950503f6b4b: GitHub CI success, including Rustfmt, strict Clippy, Rust suite, Chromium/WebKit, Windows/macOS service integration and security checks. Follow-up29d4b37cb152fb84a5573c82979dc6af74a12227is a documentation-only correction; any newer exact-head CI result should be checked separately.god-prompt-mcp@1.0.3->@1.1.1, discovery 7 -> 9 tools, invalid-candidate rollback passed.reload_mcpE2E; operator's live installation has been separately health-checked without a new production reload. No production change is required to review this PR.Operator live smoke test (November 21, 2026)
god_prompt_mcpis not necessarily the configured server key.reload_mcp({"source":"god_prompt_mcp"})failed closed withSOURCE_UNKNOWNand did not switch the connection.god-prompt-mcp,reload_mcp({"source":"god-prompt-mcp"})succeeded:diagnosticCode=OK, generation2 -> 3, GodPrompt1.4.0-checkpoint-preview.10, 23/23 unchanged tools,oldCallsDrained=true,oldCallsStillRunning=0,rollback=not_required, 2,378 ms total. A GodPromptclassify_taskcall succeeded afterward.context7reload succeeded in 1,508 ms. Post-checks showed 14/14 sources connected, unchanged main-service/browser process IDs, and both established listener ports intact. No service restart, installation, worker changes, or changes to the other parallel upgrade branches.Rollout / limitations
docs/MCP_HOT_RELOAD.mdnow explicitly distinguishes exact configured server keys from normalized catalog IDs. Client tool manifests may require a connector refresh/new session to expose newly discovered tools.Prepared as a single reviewable upstream contribution; happy to adjust scope or tests to the maintainer's preferences.