Team naming card does not paint until the next key
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with internal/tui3/wallbar.go around line 186, then reproduce the naming flow with the provided wall and team-selection steps. Trace how the naming result reaches the TUI and identify the redraw path; done means the New team card appears within a few seconds after pressing s without another key press, verified by the e2e scenario.
由索引模型根据 Issue 内容生成。
描述
Seen on: dev 837b2b0.
Behaviour
After s on the wall with two conversations selected, Naming a team for 2 conversations stayed on screen for more than 45 s with no model call. The New team card, with the name textkit, appeared only after another key press. The card should appear as soon as the name is ready.
Replication
- Build dev 837b2b0 (
git checkout 837b2b0 && make build, binarybin/codeaf), or install the dev build withcurl -fsSL https://agentfield.ai/get/devaf | bash. - Use an isolated profile:
export HOME=$(mktemp -d), exportOPENROUTER_API_KEY, and keep the default model (~deepseek/deepseek-v4-flash-latest, crew on auto). - On a busy machine set
task.max_loadto0(/settings, Tasks) so the busy-machine gate does not hold tasks. cd $(mktemp -d) && git init -q && codeaf; start two conversations and send one message in each.- Open the wall (
alt+v), select both tiles withspace, presss. - Do not touch the keyboard; time how long
Naming a team for 2 conversationsstays.
Evidence
- Screen:
Naming a team for 2 conversationsfor 45 s or more; theNew teamcard (nametextkit) after one more key. internal/tui3/wallbar.go:186draws the naming word. The redraw path was not traced.
Guessed cause
A guess from reading the code, not a confirmed diagnosis. The naming result arrives without a redraw message, so the frame is only repainted by the next key.
Acceptance
- e2e: after
s, theNew teamcard appears within a few seconds with no further key press.
Found while writing the public docs; manual text differences are in #1545.
🤖 Generated with Claude Code
- 主要语言
- Go
- 星标
- 115
- 派生
- 14
- 平均合并
- 9 小时 44 分钟
- 30 天内合并 PR
- 766
环境准备
我们还没有检查这个项目的环境配置文件。先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Agent-Field/CodeAF 的其他 Issue
-
area:chat bug sev:papercut
难度 2/5 1-3 小时 新手友好度 86/100
Agent-Field/CodeAF#1592 ·
维护者通常 1 天内回复
-
area:headless bug sev:critical
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1566 · 已指派 1 人 ·
维护者通常 1 天内回复
-
area:chat feature
难度 2/5 1-3 小时 新手友好度 88/100
Agent-Field/CodeAF#1510 ·
维护者通常 1 天内回复
-
area:tests bug
难度 2/5 1-3 小时 新手友好度 82/100
Agent-Field/CodeAF#1489 ·
维护者通常 1 天内回复
-
area:chat bug good first issue sev:papercut
难度 2/5 1-3 小时 新手友好度 78/100
Agent-Field/CodeAF#1470 ·
维护者通常 1 天内回复
查看 Agent-Field/CodeAF 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 88/100
gruntwork-io/boilerplate#329 ·
-
难度 2/5 1-3 小时 新手友好度 65/100
prime-radiant-inc/evener#3291 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 88/100
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
Netcracker/qubership-apihub-backend#582 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
维护者通常 1 天内回复