You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When an agent run fails to produce answer text, the chat UI renders the placeholder "The agent finished without a text answer." — and that placeholder string is persisted as the agent's conversation turn. Every subsequent run in that conversation replays it to the model as something the agent actually said. Captured from a live composed prompt:
Conversation so far, oldest first:
User: Propose a revision to post 1716 …
You: The agent finished without a text answer.
User: Try again
You: The agent finished without a text answer.
Effects
The model is told it previously "answered" with a meta-sentence about UI state, which it may imitate, apologize for, or reason about — context pollution that compounds with every failed run in the thread.
Persist failure turns as a distinct row type (or not at all) so the prompt composer either skips them or renders them as bracketed system context, never as You: <ui placeholder>.
Split from #517 per maintainer request (#517 (comment)).
Problem
When an agent run fails to produce answer text, the chat UI renders the placeholder "The agent finished without a text answer." — and that placeholder string is persisted as the agent's conversation turn. Every subsequent run in that conversation replays it to the model as something the agent actually said. Captured from a live composed prompt:
Effects
Suggested direction
Persist failure turns as a distinct row type (or not at all) so the prompt composer either skips them or renders them as bracketed system context, never as
You: <ui placeholder>.