CommandCodeAI / CommandCodeAI/command-code

CLI abandons to-do list tracker during execution (Potential harness failure)

未關閉
#878 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

主要語言
沒有語言資料
星號
4k
分支
350
PR 合併指標
30 天內沒有已合併 PR

描述

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

貢獻指南

這個儲存庫沒有索引到貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

先查看附加的工作階段檔案 command-code-session-f5b9bdae.md,並重現 issue 中描述的多步驟 WordPress 外掛工作流程。追蹤產生的待辦清單何時建立及更新;「done」表示已完成的工作在整個執行過程中都會被標記為已完成,且在完成時 tracker 與實際完成的工作一致。

由索引模型根據 Issue 內容生成。

評估

領域
ai, cli
Issue 類型
缺陷
難度
5/5
預估耗時
一週以上
活躍度
活躍
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。