[Bug]: Agent completed without producing any output.

[kevinjandro-pro]

Before you submit

• I searched existing issues and confirmed this is not a duplicate.
• I replaced the example text with the real behavior, reproduction steps, expected result, and version from the app's About menu or od --version.

What happened?

Cada vez que injecto una nueva orden de creacion de proyectos, este avanza y a la primera ya me sale esto: The model or provider may have returned an empty response — check the agent logs for upstream errors.

Tengo la CLI de Antigravity, Opencode y Claude Code, no corre con ninguno, cambie los modelos para intentarlo con otros y nada.

Steps to reproduce

Comenzar un proyecto normalmente, ejecutar el 'inicio' y ya aparece de entrada despues de unos segundos de ejecución del proyecto.

Expected behavior

Que comience a crear normalmente con mejoras de ejecución, uso de motion effects y menor cantidad de fallos.

Open Design version

Versión 0. 9. 0

Platform

macOS (Apple Silicon)

Logs (optional)

Screenshots (optional)

No response

Additional context

No response

[open-design-bot]

🎉 ✨ Welcome to Open Design, @kevinjandro-pro!

✨ 🔥 Lit the spark.

🌱 Your first contribution adds energy to the project. Thanks for showing up and helping Open Design grow.

💛 Thanks for helping Open Design grow. Keep building in the open. 🚀

🔗 Share on X (English) · 分享到 X（中文）

[lefarcen]

Hi @kevinjandro-pro! 👋

Welcome, and thanks for testing across Antigravity, Opencode, and Claude Code before filing — the fact that all three CLIs fail together is actually useful diagnostic signal.

The "may have returned an empty response" banner is the same error being tracked in #1855 (open, active investigation). One finding there that lines up with your v0.9.0 setup: there's a known bug at the daemon level where the memory extraction step sends its prompt incorrectly to the underlying CLI, causing runs to abort before producing any output. That fix landed in main (May 30) but the v0.9.0 release was cut before it merged. It's worth trying with the latest main build to see if it clears.

That said, I'd rather confirm with logs than guess. The daemon log on macOS is usually accessible via Help → Show Logs in the app. The key line to look for is anything mentioning [memory-llm] — that would confirm whether this is the same v0.9.0 path or something else.

One question while you grab that: when you mention "Antigravity CLI" — is this a CLI you've configured as an Execution Mode in Open Design settings, or a separate tool? Just want to make sure I have the full picture of your setup.

[lefarcen]

¿Te gustaría ayudar a investigar y resolver este bug? Comenta /claim para tomarlo.