[Bug]: Mobile shows a mid-turn progress note below "Worked for …", next to the final answer
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 76/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- mobile-dev
调研方向
从 apps/mobile/src/lib/threadActivity.ts 中的 deriveThreadFeedRunFolds 开始，然后将 mobile 的行为与 #8828 中的 web 更改进行比较。重现 prompt → Worked for → 进度备注 → 最终回答的行顺序，并使用 issue 中描述的回归测试；当 mobile 和 web 以一致的方式 fold 已确定的 thread 时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to reproduce or investigate the problem.
Area
apps/mobile
Steps to reproduce
- On the mobile app, ask an agent for something that makes it run a tool, write a short progress note, run more tools, then reply.
- Wait for the run to settle.
Expected behavior
The same as web since #8828: prompt → Worked for … → final answer, with the progress note inside the fold.
Actual behavior
Mobile shows prompt → Worked for … → progress note → final answer. The note sits under the fold as if it came after all the work, and reads as the first paragraph of the final answer, while most of the work happened between the two.
Cause: deriveThreadFeedRunFolds in apps/mobile/src/lib/threadActivity.ts still exempts the run's first assistant message from the fold (the rule #7723 added for both clients). #8828 removed that rule from web only, so web and mobile now fold the same thread differently.
Impact
Minor, but misleading: on the phone the order of what the agent did and said is misrepresented in every settled run that starts with a tool call and narrates once.
Version or commit
main at 00eb8f6183.
Environment
Android phone app connected to a Windows desktop server, Claude provider.
Workaround
Expand the fold.
Note: the open draft #14698 proposes the opposite direction for both clients (keep every assistant message visible). I'd argue for keeping the fold: a settled turn that reads prompt → Worked for → answer is much easier to scan than a transcript with every interim note in it. Anything an interim note says that matters belongs in the final message, and that is the agent's job to restate there. Either way, web and mobile should agree. I have a two-file fix ready that ports #8828 to mobile, with a test that reproduces the row order above (red on main, green with the fix), and can open it if this direction is the one you want.
- 主要语言
- TypeScript
- 星标
- 24.8k
- 派生
- 6.4k
- 平均合并
- 13 小时 9 分钟
- 30 天内合并 PR
- 271
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
pingdotgg/t3code 的其他 Issue
-
bug via-triage
难度 2/5 1-3 小时 新手友好度 62/100
pingdotgg/t3code#17157 · 1 条评论 ·
维护者通常 1 天内回复
-
bug via-triage
难度 2/5 1-3 小时 新手友好度 76/100
pingdotgg/t3code#17013 · 1 条评论 · 1 个 reaction ·
维护者通常 1 天内回复
-
documentation via-triage
难度 1/5 1-3 小时 新手友好度 83/100
pingdotgg/t3code#16995 · 1 条评论 ·
维护者通常 1 天内回复
-
documentation via-triage
难度 1/5 1 小时以内 新手友好度 88/100
pingdotgg/t3code#16988 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
相似的 Issue
-
[bug] diagnostics.dumpBody：Buffer 形态请求（透传 lane）跳过 dumps/ 落盘，仅留 raw/-unknown-可能已有人在做 @ranxianglei 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 62/100
ranxianglei/billion-context#2421 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
platformatic/mcp#216 ·
维护者通常 1 天内回复
-
pending triage
难度 2/5 1-3 小时 新手友好度 76/100
nuxt/test-utils#1842 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
MoonshotAI/kimi-code#4146 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 85/100
farbenmeer/tapi#531 ·