Resolve pinned Codex MCP protocol compatibility in Connect (#152, #160)

Chiusa
  • Qualcosa non va?
#460 9 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@PelikanFix16 ci sta già lavorando.

Dal 10/10/2026.

  • #589 di @PelikanFix16 — integrata

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

Part of #152 (real-client compatibility) and #160 (supported built-in onboarding), following the independent review of PR #396. Milestone: the complete application and release.

The pinned real Codex rust-v0.160.1 asks for MCP 2025-06-18 by default. Flux currently accepts 2026-07-28; the tested connection needs --enable mcp_2026_07_28. This is recorded in development docs and the opt-in client fixture, but the product Connect flow does not yet handle the compatibility choice. Listing tools successfully does not complete #160's Start/Resume acceptance.

Outcome: choose, record and implement a truthful supported connection path for the pinned Codex client, within the existing MCP authorization and co-work contracts.

Acceptance:

  • Reproduce the default and flagged handshake with the pinned real client in Docker. Record exact client/server heads, protocol offers/results and dated primary evidence.
  • Independently review and record the compatibility decision before changing the public protocol contract: support the older protocol with verified equivalent semantics, or integrate the required invocation/flag in Connect. Preserve the existing role/scope, revocation, standing-grant and required-client-feature boundaries.
  • Make the supported invocation and any unsupported state clear in the built-in connection path. No README, manual prompt or silent protocol downgrade counts as supported onboarding. Full supplied Start/Resume remains #160's acceptance work.
  • Verify the selected path plus unsupported-version rejection and current authorization/revocation controls with the real client; add meaningful regression coverage for the changed boundary.

Owner: @PelikanFix16. Independent evaluator: @Zamojski5. Reuse the existing #152/#160 client harness and transport, without a second implementation of these domains. Source finding: the independent review on PR #396 at 699d0099e4ac7f2f2b804d00a4f09f61ce65c8dd.

Lingua principale
TypeScript
Stelle
3
Fork
0
Merge medio
19h 42m
PR unite (30g)
383

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ColdPhase/flux

Tutte le issue di ColdPhase/flux

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.