# Agent replies/thinking/reasoning in IDE missing **URL:** \ **Category:** Google Antigravity\ **Tags:** thinking\ **Created:** [June 10, 2026, 1:27pm UTC](https://discuss.ai.google.dev/t/agent-replies-thinking-reasoning-in-ide-missing/170622 "2026-06-10T13:27:42Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![QueueQ](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/queueq/32/35100_2.png) [@QueueQ](https://discuss.ai.google.dev/u/QueueQ)\ **Post date:** [June 10, 2026, 1:27pm UTC](https://discuss.ai.google.dev/t/agent-replies-thinking-reasoning-in-ide-missing/170622/1 "2026-06-10T13:27:42Z")
I’ve noticed that while the agent is working, it will often say some stuff I definitely want to read. Breakthroughs, reasonings, responses, etc., that will only be available during the current Working… task, then it will disappear and not be in any of the expandable history once it’s done working. Any idea how to see the full output anywhere? The export chat .md is also missing those messages. ---
**Author:** ![Wingray\_SHU](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/wingray_shu/32/57540_2.png) [@Wingray\_SHU](https://discuss.ai.google.dev/u/Wingray_SHU)\ **Post date:** [June 11, 2026, 5:40am UTC](https://discuss.ai.google.dev/t/agent-replies-thinking-reasoning-in-ide-missing/170622/2 "2026-06-11T05:40:21Z")
In simple terms, this is an anomaly inherent to Antigravity—or, if you prefer, a peculiar ‘feature.’ The client intercepts the `thought:` React tag designated within the agent’s system prompt, subsequently truncating and obscuring it. Should you wish to reveal this hidden content, you can adapt any React template from Hugging Face and inject it as a workflow prompt. By specifying a custom React tag, the client’s interception service will falter, thereby rendering the raw thoughts directly within the conversation. The caveat, however, is that disabling this client-side listener may inadvertently disrupt the structured output of the agent’s command invocations, ultimately causing console command executions to fail. Consequently, a more prudent approach is to refrain from viewing the agent’s raw responses. Instead, employ global or workspace rules to mandate that the agent document its session logs in a designated location, such as a `work_log.md` file. Bear in mind, however, that this alternative will incur a significantly higher cost in output token consumption. ---
**Author:** ![QueueQ](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/queueq/32/35100_2.png) [@QueueQ](https://discuss.ai.google.dev/u/QueueQ)\ **Post date:** [June 11, 2026, 8:17pm UTC](https://discuss.ai.google.dev/t/agent-replies-thinking-reasoning-in-ide-missing/170622/3 "2026-06-11T20:17:53Z")
Thanks for that insight, I had similar thoughts about making the agent to output its thoughts elsewhere. Will definitely play around with both options, was just wondering if there was something I was missing in the settings somewhere thank you. ---
**Author:** ![Thom\_Porter](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/thom_porter/32/131026_2.png) [@Thom\_Porter](https://discuss.ai.google.dev/u/Thom_Porter)\ **Post date:** [June 12, 2026, 9:02pm UTC](https://discuss.ai.google.dev/t/agent-replies-thinking-reasoning-in-ide-missing/170622/4 "2026-06-12T21:02:53Z")
+1 to this! I’ve used the reasoning of models on many occasions, and frequently have added to the rules based on what I see. And sometimes I’m just curious how it came to a particular decision, sometimes I even learn from it, and sometimes I create a new rule. 😉 Would love to have the ability to see the reasoning back! ---
**Author:** ![matstops](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/matstops/32/120396_2.png) [@matstops](https://discuss.ai.google.dev/u/matstops)\ **Post date:** [June 13, 2026, 2:46am UTC](https://discuss.ai.google.dev/t/agent-replies-thinking-reasoning-in-ide-missing/170622/5 "2026-06-13T02:46:37Z")
They’ve known about this for weeks and haven’t done anything about it, because your hidden response used up tokens, and if you ask for a repeat, it’ll use up more tokens, and the AI will cheekily reply that something must have glitched and that’s why you didn’t see the response—because it’s already been trained for this very situation 😉 ---
**Author:** ![QueueQ](https://d1dlmcr85iqnpo.cloudfront.net/user_avatar/discuss.ai.google.dev/queueq/32/35100_2.png) [@QueueQ](https://discuss.ai.google.dev/u/QueueQ)\ **Post date:** [June 16, 2026, 7:08pm UTC](https://discuss.ai.google.dev/t/agent-replies-thinking-reasoning-in-ide-missing/170622/6 "2026-06-16T19:08:47Z")
Eh we’re a month out from their major update separating the IDE from 2.0, I wish it could be better, but I expect some issues. I’m leaning towards this being a bug rather than a trained feature lol. Haven’t even tested whether this works better in the non-IDE version either. edit: I have been trying out the non-IDE one for about an hour and the thoughts do stay readable in that agent view. Suppose I’ll do that for the longer tasks I give it so I can see those.