[codex] repair stale MCP registrations - #223
Merged
Merged
Conversation
morluto
marked this pull request as ready for review
July 29, 2026 12:15
|
Bugbot is not enabled for your account, so this pull request was not reviewed. Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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.
Problem
GitContribute previously generated MCP registrations that launched
gitcontribute mcp. The current CLI requiresgitcontribute mcp serve --transport=stdio, so those registrations now exit during MCP initialization and surface as a generic handshake failure in clients such as Codex.Current setup already writes the canonical launcher, but the surrounding lifecycle paths did not recognize stale registrations:
doctorchecked only whether a GitContribute entry existed.upgrade --checkparsed launcher arguments but classified registrations only by executable version.upgrade --yestherefore had no repair path when the executable was current but its arguments were stale.Fix
Introduce one client-neutral registration inspection contract with
absent,current, andstalestates. Canonical launcher construction and validation now cover both the durable absolute executable and the complete MCP argument vector.Use that inspection consistently across lifecycle operations:
doctorreports an existing stale or malformed registration as a required diagnostic failure and points users to setup for repair.upgrade --checkreportsregistration repair requiredand identifies stale clients.upgrade --yesrepairs stale registrations as one rollback-safe activation, preserves each configured executable path, verifies the resulting entries, and reports the clients that must restart.The obsolete
gitcontribute mcpinvocation is not restored as a compatibility alias.Safety and compatibility
Inspection remains read-only. Repair requires the existing explicit
upgrade --yesor setup consent boundary, never creates registrations, preserves unrelated client configuration, and rolls back every selected registration if activation or verification fails.No dependencies were added.
Validation
make verifynpm run test:npm)