Collapsed "Worked for" turn stacks its "Context compacted" dividers out of place

未关闭 适合新手
#33,825 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

从 MessagesTimeline.logic.ts 的第 1130–1143 行附近开始,这里在折叠过程中会跳过压缩行。追踪折叠过程如何确定某个轮次收起时哪些行仍然可见,然后检查时间线收起和展开时的行为。完成标准是:收起时,多个压缩分隔符不再堆叠在 Worked-for 行下方。

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

描述

via-triage
What happened

When a finished turn that compacted twice is collapsed, both "Context compacted" rows stay visible, stacked directly under "Worked for 1h 16m 53s". They look like one line duplicated. Expanding the turn shows they're far apart, with tool calls and messages before, between and after them. Clicking a divider only selects its text.

CollapsedExpanded
Collapsed turn: two Context compacted rows stacked under Worked for Expanded turn: the same two rows sit far apart
Diagnosis

The fold skips compaction rows on purpose (MessagesTimeline.logic.ts ~L1130-1143, isCompaction -> continue). Once everything around them is hidden, they lose their position, and they carry no title, token count or time to tell them apart. One fix would be to fold them with the turn and show "compacted 2x" on the Worked-for row.

Steps to reproduce
  1. Run a long turn that compacts at least twice.
  2. Let it finish so it collapses.
  3. The compaction rows sit stacked under "Worked for...".
  4. Click "Worked for": the rows spread out.
Version

0.1.8-nightly.20261109.4433 (desktop app and its local server)

Environment

macOS 27, arm64; desktop app; Codex thread (GPT-6.1 Sol)

Evidence
Screen recording: collapsed at 0.0 s and 13.03 s; expanded at 1.3 s. The two dividers are about 14 rows apart when expanded. Stills attached.
Related issues

None found.

Fix applied or workaround

None.

Filed by

Claude Opus 5.5 via Claude Code (T3 Code 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 摘要。