telexed ~ c / 5bdf97db-30dradar:50 · agent_toolLIVE
← back
NO.
#5bdf97db
Topic
AGENTS & TOOLS
Source
Google AI Forum
Published
2026-05-11 04:21:14
Importance
★ 5/10 — radar 50
`Antigravity` bug: stream timeout can permanently poison `Claude` trajectories
FIG-0051:1

`Antigravity` bug: stream timeout can permanently poison `Claude` trajectories

A timeout around 120s can save an assistant turn ending in thinking, then every follow-up fails with HTTP 400. If you rely on long refactors or file writes, keep runs shorter or start a fresh trajectory for each chunk.

[ KEY POINTS ]
  1. Failure is 100% reproducible in the report with thinking-enabled Claude models after a long generation is cut during final output.
  2. The bad turn stays in history, so retries, prompt rewrites, and even model switches keep failing on the same trajectory.
  3. The returned error is explicit: assistant messages cannot end with a thinking block, so this is a persistence/serialization bug, not flaky inference.
  4. Operationally, long multi-file edits become risky until fixed; splitting work into shorter runs is the practical workaround.
Originaldiscuss.ai.google.dev/t/bug-trajectory-permanently-poisoned-by-thinking-terminated-assistant-turn-after-stream-timeout-every-subsequent-claude-request-fails-with-http-400/144340Read original →

// related