Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

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

オープン
  • 何か問題がありますか？
#1,515 コメント 0 件 リアクション 0 件 担当者 1 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

@Alan-Cha がすでに取り組んでいます。

2026年10月27日 から。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
go
領域
backend-api-design

調査の方向性

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.

索引モデルが issue の本文から書いたものです。

説明

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]

主要言語
Go
スター
21
フォーク
43
平均マージ
14時間 26分
マージ済み PR（30日）
239

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

rossoctl/cortex のほかの issue

rossoctl/cortex の issue をすべて見る

似ている issue

Go の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。