feat: MCP 2026-07-28 dual-era protocol support (v1.11.0) - #28
Merged
Merged
Conversation
Implement the latest MCP revision alongside the classic lifecycle: - New src/mcp/lifecycle.rs: per-request era detection via _meta["io.modelcontextprotocol/protocolVersion"], stateless modern handling, legacy initialize version negotiation, server/discover (DiscoverResult with supportedVersions/capabilities/instructions), UnsupportedProtocolVersionError (-32022), resultType + ttlMs/cacheScope cache hints on cacheable endpoints, serverInfo in result _meta. - Legacy wire format stays byte-identical (pinned by tests); ping is legacy-only per the revision's removal. - Tool annotations (readOnlyHint/destructiveHint/idempotentHint/ openWorldHint) on all 52 tools via ToolHints. - Verified against the official 2026-07-28 schema and live E2E against the ChatGPT desktop extension (Chrome/Edge rebrand: pipe name and protocol unchanged); docs updated for the ChatGPT desktop app naming. - Bump version to 1.11.0 (Cargo.toml, npm/package.json, Cargo.lock), CHANGELOG, ROADMAP, ARCHITECTURE (dual-era decisions), AGENTS source map, README EN/zh (protocol support section, Edge support, rebrand). Co-authored-by: Cursor <cursor@vectorcontrol.tech>
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
1 participant
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.
Summary
2026-07-28as a dual-era server: legacy lifecycle (2024-11-05…2025-11-25, byte-compatible) and the new stateless era (per-request_metaprotocol version,server/discover,resultType,ttlMs/cacheScopecache hints,UnsupportedProtocolVersionError-32022).readOnlyHint/destructiveHint/idempotentHint/openWorldHint) to all 52 tools, plusinitializeversion negotiation and serverinstructions.codex-browser-usepipe name and JSON-RPC protocol are unchanged — verified live against the current extension on Edge; no functional impact on the bridge.Verification
cargo fmt --check,cargo clippy --locked --all-targets -- -D warnings— cleancargo test --locked— 99 tests pass (incl. 8 lifecycle + 5 protocol-era + annotation tests)npm --prefix npm test— passscripts/check-agent-surface.js/check-actions-pinned.js/check-release-contract.js— all okinitializeecho,server/discover(5 supported versions), moderntools/list(52 tools + annotations + cache hints),codex_doctorhealthyTest plan
v1.11.0→ release workflow publishes GitHub Release + npm@delicious233/codex-browser-bridge@1.11.0