Trailing mojibakes + internal turn artifacts in Codex agent reply

未关闭 适合新手
  • 哪里不对？
#33,489 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
72/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
typescript
领域
backend, desktop

调研方向

阅读 CodexAdapterV2.ts 第 5280–5284 行附近的代码，并追踪 item.text 如何到达桌面端渲染器。检查对 t3-citation:// 和 Codex 指令的现有处理，然后查找相关的 provider 或渲染测试。完成的标准是：Codex 原生的 citeturn/view 标记和 【turnXviewY】 令牌不再出现在用户可见的回复中，同时有意义的文本保持完整。

由索引模型根据 Issue 内容生成。

描述

via-triage
What happened

Trailing Private-Use-Area (PUA) glyphs and internal Codex turn-view artifacts leak into the user-visible chat text on the desktop app after Codex agent sessions. The rendered text shows markers such as:
citeturn918416view0turn291398view2
These artifacts appear sometimes in regular chat with a Codex-backed agent, always trailing the meaningful text, and are made up of internal provider identifiers that should have been stripped before display.

Diagnosis

Source: The markers originate from the Codex app-server provider, not T3 Code's own citation system. They come from two sources within the Codex protocol:
(1) item/completed agent message events wrapped in PUA sentinels containing tokens citeturn<N>view<V> (e.g., citeturn918416view0, turn291398view2). These appear in provider event logs like events.mcp-launch-cf7cfe43c61cf9092fe657358db496313e10d4c34dc67362ea4548885879ea41.log:4014.
(2) MCP tool-call result text — e.g., 【turn141338view0】 from web/browse tool outputs. These appear in logs like events.mcp-launch-561cae086a4946b04164cb05a82358c59c50dba226fd45362a693a6812d8b126.log:1002.

Why they leak: In CodexAdapterV2.ts:5280-5284, the server passes Codex's raw item.text straight through with no stripping of provider-internal markers. The client-side renderer only handles T3 Code's own t3-citation:// citations and Codex codex-file-citation / artifact-template / codex-followup directives. It does not strip Codex's native citeturn/view or 【turnXviewY】 syntax, so they render verbatim.

Steps to reproduce
  1. Start a Codex agent session on the desktop app (local server connection)
  2. Chat with the agent for any length of time
  3. Observe agent replies — trailing garbled PUA glyphs and citerviewview / 【turnXviewY】 tokens appear appended to or embedded in the message text
  4. No deterministic trigger — happens intermittently, but consistently in Codex sessions
Version

T3 Code nightly v0.1.8-nightly.20261109.4399

Environment

OS: Windows 11 Pro, Node v24.22.1, triage CLI version 0.1.8-nightly.20261109.4399, server process running at http://127.0.0.1:3773, connecting the desktop app to a local server

Evidence
- `events.mcp-launch-cf7cfe43c61cf9092fe657358db496313e10d4c34dc67362ea4548885879ea41.log:4014` — `turn918416view0`, `turn291398view2`, `turn564001view0`, `turn345183view4` all in one `item/completed` agent message event
- `events.mcp-launch-561cae086a4946b04164cb05a82358c59c50dba226fd45362a693a6812d8b126.log:1002` — `turn974882search0`, `turn141338view0` from MCP search tool results
- `events.f92e11fb-7e1a-47eb-abce-f636c7dc0f7d.log:2940` — `turn275451search1` from another Codex session
Related issues

No response

Fix applied or workaround

None known — this is a rendering bug in the client's text pipeline where Codex provider-internal markers are not filtered before display.

Filed by

claude (sonnet-5) via t3 triage

主要语言
TypeScript
星标
24.8k
派生
6.4k
平均合并
13 小时 9 分钟
30 天内合并 PR
187

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

pingdotgg/t3code 的其他 Issue

查看 pingdotgg/t3code 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。