CLI abandons to-do list tracker during execution (Potential harness failure)
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
Start by reviewing the attached command-code-session-f5b9bdae.md session file and reproduce the multi-step WordPress plugin workflow described in the issue. Trace when the generated to-do list is created and updated; done means completed tasks are marked as such throughout execution and the tracker matches the actual work at completion.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from CommandCodeAI/command-code
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#903 · 2 comments ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#855 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
CommandCodeAI/command-code#841 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#655 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
CommandCodeAI/command-code#608 ·
All issues in CommandCodeAI/command-code
Similar issues
-
ai-observability bug team/ai-observability
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
dair-ai/Prompt-Engineering-Guide#810 · 1 comment ·
-
[addtool] DeepZero Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
gwen001/offsectools_www#2055 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UKGovernmentBEIS/inspect_evals#2503 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
google-gemma/gemma-skills#13 ·