Repository navigation
Codex plugin 0.3.1: bundle devtools 0.3.1 with stored MCP names - #2
Merged
Merged
Conversation
Pin @dev-mainsequence/devtools 0.3.1 (lockfile integrity from the registry's dist.integrity) and release the plugin as 0.3.1. devtools 0.3.1 stores a connected MCP's names (name, display_name, code_repository_branch_uid) in the shared mcp-connections.json when mcp-add saves it and lists them without a backend request; a connection saved by an earlier version is completed by the first listing that can read it. The readable /ms output labels the new connection fields; --json passes them to the mainsequence-mcp skill unchanged, and the skill and user guide describe them. CI no longer names a devtools source branch now that the pin is on the registry. Verification is recorded in docs/codex-verification.md (release check, verify:codex and verify:codex:reload in isolated Codex homes). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
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.
Why
devtools 0.3.1 stores a connected MCP's names with the saved connection, so hosts can label a connection without backend requests. Both plugins share
mcp-connections.json; the Codex plugin benefits once it bundles 0.3.1, and until then its devtools 0.3.0 drops the new fields from its in-memory rows.What changes
@dev-mainsequence/devtoolspinned to 0.3.1 inpackage.jsonandpackage-lock.json(integrity fromnpm view @dev-mainsequence/devtools@0.3.1 dist.integrity); plugin version 0.3.1 in the package and the manifest.docs/codex-verification.md:mcp-addstoresname,display_nameandcode_repository_branch_uidwith the saved connection;mcp-listreturns them without a backend request; a connection saved by an earlier version is completed by the first listing that can read it. The user guide and themainsequence-mcpskill describe the stored labels./msoutput labels the new connection fields (Release ID,Repository,Repository branch ID);--jsonpasses rows through unchanged. One new test case covers both.DEVTOOLS_SOURCE_REF: the pinned devtools is on the registry, andscripts/install-devtools.cjsfalls back to the pin's release tag only for an unpublished pin.Verification
Node 22.22.0, npm 10.9.4:
npm run release:checkpasses (type-check, build from the registry archive, 15 tests, release metadata, standalone and npm archives, the npm archive exercised as Codex installs it).npm run verify:codex(this build installed from the local marketplace into an isolatedCODEX_HOME, Codex CLI 0.163.0: 13 prompt cases, 2 sync cases, 0 real model requests) andnpm run verify:codex:reloadpass. The hook definition is unchanged, so its trusted hash is the same as in 0.3.0.After merging: tag
v0.3.1(the release workflow publishes with npm trusted publishing), then point the marketplace entry in mainsequence-devtools at 0.3.1.🤖 Generated with Claude Code