CommandCodeAI / CommandCodeAI/command-code

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

Aperta
#408 0 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@naymurdev ci sta già lavorando.

Dal 29/6/2026.

/design p1
Lingua principale
Nessun dato sulla lingua
Stelle
4k
Fork
350
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

/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.

Guida per i contributori

Nessuna guida per i contributori indicizzata per questo repository

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.