<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>AI Agents on Vinh Thang's AI Tech Notes</title><link>https://vinhthang.dev/tags/ai-agents/</link><description>Recent content in AI Agents on Vinh Thang's AI Tech Notes</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 05 Sep 2026 14:00:00 +0700</lastBuildDate><atom:link href="https://vinhthang.dev/tags/ai-agents/index.xml" rel="self" type="application/rss+xml"/><item><title>Securing Agentic Orchestration: Building the Attention Guard 2.0 State Machine</title><link>https://vinhthang.dev/posts/attention-guard-2/</link><pubDate>Sat, 05 Sep 2026 14:00:00 +0700</pubDate><guid>https://vinhthang.dev/posts/attention-guard-2/</guid><description>&lt;p&gt;As autonomous AI agents evolve from isolated chatbots into orchestrators of complex, multi-pass software engineering tasks, the boundaries of execution become critical. In the &lt;strong&gt;Antigravity&lt;/strong&gt; ecosystem, we rely heavily on specialized subagents—like &lt;code&gt;DeepCoder&lt;/code&gt; and &lt;code&gt;DeepInvestigator&lt;/code&gt;—to autonomously navigate codebases, test hypotheses, and execute shell commands.&lt;/p&gt;
&lt;p&gt;But what happens when an agent hallucinates a success? What happens when a long-running subagent hangs indefinitely? How do we prevent a deeply nested execution worker from going rogue and launching its own recursive subagents?&lt;/p&gt;</description></item></channel></rss>