CommandCodeAI / CommandCodeAI/command-code

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

Aberta
#878 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Linguagem predominante
Sem dados de linguagem
Estrelas
4k
Forks
350
Métricas de merge de PRs
Nenhum PR com merge em 30d

Descrição

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

Guia de contribuição

Nenhum guia de contribuição indexado para este repositório

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Direção de pesquisa

Comece revisando o arquivo de sessão anexado command-code-session-f5b9bdae.md e reproduza o workflow de várias etapas do plugin WordPress descrito na issue. Rastreie quando a lista de tarefas gerada é criada e atualizada; “done” significa que as tarefas concluídas são marcadas como tal durante toda a execução e que o tracker corresponde ao trabalho realizado de fato ao final.

Escrita pelo modelo de indexação a partir do texto da issue.

Avaliação

Domínio
ai, cli
Tipo de issue
Bug
Dificuldade
5/5
Tempo estimado
Mais de uma semana
Status de atividade
Ativa
Clareza
Precisa de esclarecimento
Facilidade para iniciantes
25/100

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.