Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

WebSocket turns carry only new input, so conversation-level plugins see less of a Codex session

Aperta
  • Qualcosa non va?
#1,515 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@Alan-Cha ci sta già lavorando.

Dal 27/10/2026.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
go
Ambito
backend-api-design

Direzione di ricerca

Read the implementation from #1467 and trace how WebSocket turns are parsed into Extensions.Inference.Messages; compare that with the HTTPS request path and the handling of previous_response_id. Decide which of the three proposed approaches preserves the intended plugin behavior, then identify the affected relay and plugin tests. Done means conversation-level plugins receive the expected context or can reliably detect incremental input.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Follow-up to #1467, which carries Codex's Responses API WebSocket and parses each turn on it.

The limitation

Over HTTPS, every Codex turn is a POST whose body carries the whole conversation. Over the WebSocket, only the first turn on a socket does. Every later turn carries only the new input items, plus a previous_response_id naming the turn before. The server keeps the earlier context. That is part of why Codex prefers the socket.

#1467 parses each turn exactly as its body reads, so on a socket's later turns Extensions.Inference.Messages holds only the delta, not the conversation.

Who it affects

  • Unaffected: inference-parser's model, tokens, cost and tool calls (these come from the response), and tool-prune (each turn carries its own tool list).
  • Affected: any plugin that judges the conversation as a whole, for example ibac reading the user's intent across turns, context-guru, or a policy (opa, cpex) written against input.inference.messages. Over the socket such a plugin sees less than it would over HTTPS for the same session.

Codex runs on laptop installs today, where none of those are in the default pipeline. So nothing is broken for current users, but a deployment that enables them for Codex would get weaker coverage without any sign of it.

Possible fixes

  1. Rebuild the conversation per socket. The relay already sees every turn's input and every response's output items. It could keep a running transcript per socket and present plugins the full message list, as an HTTPS body would carry. Cost: memory per open socket, and reproducing what the server reconstructs from previous_response_id.
  2. Flag the turn as incremental (for example, an Incremental field on InferenceExtension), so a conversation-level plugin can tell it is seeing a delta and decide for itself.
  3. Fall back for those pipelines. When the chain contains a plugin that needs the whole conversation, decline the socket (listener.responses_websockets: decline), so Codex uses HTTPS. That is available today as a manual setting.

Refs #1467, #1365.

Assisted-By: Claude (Anthropic AI) [email protected]

Lingua principale
Go
Stelle
21
Fork
43
Merge medio
14h 26m
PR unite (30g)
239

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 rossoctl/cortex

Tutte le issue di rossoctl/cortex

Issue simili

Altre issue su Go

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.