CommandCodeAI / CommandCodeAI/desktop

[Bug]: Muse Spark 1.2/contributor: any image attachment → 400 Storage limit — 100% reproducible, session killed permanently

Abierto
#31 2 comentarios 0 reacciones 1 asignado Ver en GitHub

@aliarain ya está trabajando en esto.

Desde el 13/8/2026.

bug
Lenguaje dominante
Shell
Estrellas
80
Forks
2
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

GUI version

0.1.10

Operating system

macOS (Apple silicon)

Reproduction steps

Description:
Attaching any image (screenshot, PNG, JPEG) while using meta/muse-spark-1.2-contributor instantly returns Error: 400 Storage limit exceeded for this team. Session is permanently corrupted for Muse — switching to other models works, switching back to Muse fails even on text-only. Only a fresh session (with no images) recovers.

100% reproducible across 4 independent sessions:

Session Images 400 at Trace ID
Tf3BaAudNVkGxV74QU0o (fresh) 1 msg #2 0e8fce61
dpItxAmlZY3v-o-ahLPis (fresh, new image) 1 msg #2 48a01729
tfLX0JirnnSoLWh-CQqvy (290 text fine) 1 msg #291 89ad66e8 +6
zfEGNSmYkrfa08PeijbGq (39 text fine) 1 msg #40 518db359 +7

Steps: 1. Start session with Muse Spark 1.2 → 2. Attach any image → 3. 400 immediately → 4. continue / new text message → same 400 → 5. Switch to Luna/DeepSeek → works → 6. Switch back to Muse → 400 (text-only).

Expected behavior

Expected: Image attachment works, or at minimum doesn't permanently destroy session state

Actual behavior

Actual: Generic message + loop, no recovery

Workaround: New session works, old history stuck on disk at ~/.commandcode/projects//tfLX0JirnnSoLWh-CQqvy.jsonl — verify: grep "Storage limit" ~/.commandcode/projects//tfLX0JirnnSoLWh-CQqvy.jsonl

Screenshots, recordings, or sanitized logs

Session: tfLX0JirnnSoLWh-CQqvy
Trace IDs: 0e8fce6125729e91e716906b0a58730c, 48a017296f46704edb850b9ed3fac2db, 89ad66e86279a2f6654289018e5761a5, 31a625e2b0f31aa26da7a3114fddba97, 8c530677ed71227a3cd332de89c4af0b, 67ea571eb49b6de3d40dd977cdbfc309, 61d73f0df6880ef01bb28530a37ad6ef, ecb61e3f699198865c2f57882fda2ecf, 2eed9a6aa35a128ea9620d10cdf31261, 518db359b93f50cbd284e250fb4915c7, 9289e0a70e72410d0fd4964f9c21ac85

Image Image Image Image
Safety check
  • I removed credentials and private project information from this report.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.