CommandCodeAI / CommandCodeAI/command-code
CLI abandons to-do list tracker during execution (Potential harness failure)
Nadie ha tomado este issue todavía.
- Lenguaje dominante
- Sin datos de lenguaje
- Estrellas
- 4k
- Forks
- 350
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Línea de trabajo
Comienza revisando el archivo de sesión adjunto command-code-session-f5b9bdae.md y reproduce el flujo de trabajo de varias etapas del plugin de WordPress descrito en el issue. Rastrea cuándo se crea y se actualiza la lista de tareas generada; «done» significa que las tareas completadas se marcan como tales durante toda la ejecución y que el tracker coincide con el trabajo real al finalizar.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Área
- ai, cli
- Tipo de issue
- Error
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Estado de actividad
- Activo
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 25/100