CommandCodeAI / CommandCodeAI/command-code

Bug: /design skill hangs on longer prompts regardless of flags

Aberta
#408 0 comentários 0 reações 1 responsável Ver no GitHub

@naymurdev já está trabalhando nisso.

Desde 29/6/2026.

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

Descrição

/design skill hangs on longer prompts regardless of flags

Environment:

  • Command Code v0.27.0
  • Model: default (taste-1)
  • Platform: Linux (x64), Node v24.15.0
  • Host: local machine

Steps to reproduce:

  1. Run cmd with the /design skill
  2. Submit a comprehensive design review prompt (covering UI audit of a multi-page application)
  3. Command Code hangs indefinitely — no progress, no output, no error
  4. Must be killed externally (SIGKILL)

Observed behavior:

  • /design works reliably with --max-turns 10 and a short prompt (2-3 sentences)
  • With longer prompts (describing a full site review) or without --max-turns limit, the process freezes after the first response
  • The hang is not a timeout — it persists for hours with no CPU activity
  • Occurs regardless of --max-turns, -p (non-interactive), or interactive flags
  • No error logs are written; no crash report

Expected behavior:

  • /design should process prompts of any reasonable length
  • Should handle comprehensive design reviews spanning multiple pages/sections
  • Should either complete, provide partial output, or return a clear error

Impact:
Blocks using /design for meaningful site-wide design audits. Only trivial single-component prompts work.

Additional context:
This was discovered while trying to run a full-site design audit of a React 19 application. The same review was successfully completed using alternative tools (impeccable detector + manual UI audit scripts), confirming the prompt content itself is valid.

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.

Avaliação

Esta issue ainda não foi avaliada.

Receba novas issues na sua caixa de entrada

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