CLI abandons to-do list tracker during execution (Potential harness failure)
还没有人认领这个 Issue。
评估
调研方向
首先查看附加的会话文件 command-code-session-f5b9bdae.md,并复现 issue 中描述的多步骤 WordPress 插件工作流。跟踪生成的待办列表何时创建和更新;“done”表示已完成的任务在整个执行过程中都被标记为已完成,并且在结束时 tracker 与实际完成的工作一致。
由索引模型根据 Issue 内容生成。
描述
Summary
While building a WordPress plugin, the Command Code CLI generated a to-do list but stopped updating it before completion. The CLI continued working past the point of updating the tracker, leading to a stale list. When asked why it stopped when work was incomplete, the CLI admitted to a process failure, stating it stopped maintaining the tracker rather than the work itself. This appears to be a harness failure regarding state and task management.
Expected Behavior
The CLI should continuously maintain and update its to-do list tracker as it progresses through tasks, marking items as complete when finished to ensure the tracker remains synchronized with actual work progress.
Actual Behavior
The CLI stopped updating the tracker, leaving items pending even after they were completed. When prompted about the stalled list, the CLI responded:
"Direct answer: I didn't stop the work — I stopped maintaining the tracker. The last pending item was 'remaining integrations,' which I'd finished long ago, but I never marked it done and then kept working past the point where I was updating it. That's a real process failure: a stale list is worse than no list. But chasing it down was worth it, because that item was hiding a real problem."
Steps to reproduce the issue
Prompt Command Code CLI to build a multi-step project (e.g., a WordPress plugin).
Allow the CLI to generate a to-do list to track its progress.
Observe the CLI's progress as it completes tasks without checking them off the generated list.
Ask the CLI why it stopped when the list was not completed to trigger the state acknowledgment.
Command Code Version
1.55.1
Operating System
Linux
Terminal/IDE
tmux
Shell
bash
Session file (optional)
command-code-session-f5b9bdae.md
Fix prompt (optional)
No response
Additional context
No response
- 主要语言
- 没有语言数据
- 星标
- 4k
- 派生
- 350
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
这个仓库没有索引到贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
CommandCodeAI/command-code 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
CommandCodeAI/command-code#855 ·
-
难度 2/5 1-3 小时 新手友好度 78/100
CommandCodeAI/command-code#841 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
CommandCodeAI/command-code#655 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 68/100
CommandCodeAI/command-code#608 ·
-
难度 3/5 1-2 天 新手友好度 70/100
CommandCodeAI/command-code#893 ·
查看 CommandCodeAI/command-code 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
use-agent-os/agent-os#3263 ·
-
[Bug]: context-limit error parsing has no pattern for llama.cpp's "context size (N tokens)" phrasing 未关闭area/compression area/local-models area/sessions comp/agent duplicate P2 sweeper:risk-session-state type/bug
难度 2/5 1-3 小时 新手友好度 82/100
NousResearch/hermes-agent#117793 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 82/100
-
难度 2/5 1-3 小时 新手友好度 84/100
-
难度 2/5 1-3 小时 新手友好度 75/100
BasedHardware/omi#15236 · 1 条评论 ·