<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Avneesh Jadhav]]></title><description><![CDATA[Avneesh Jadhav]]></description><link>https://avneeshjadhav.hashnode.dev</link><image><url>https://cdn.hashnode.com/res/hashnode/image/upload/v1593680282896/kNC7E8IR4.png</url><title>Avneesh Jadhav</title><link>https://avneeshjadhav.hashnode.dev</link></image><generator>RSS for Node</generator><lastBuildDate>Sun, 11 Oct 2026 12:51:21 GMT</lastBuildDate><atom:link href="https://avneeshjadhav.hashnode.dev/rss.xml" rel="self" type="application/rss+xml"/><language><![CDATA[en]]></language><ttl>60</ttl><item><title><![CDATA[Agent Autonomy over Long Horizons]]></title><description><![CDATA[Agent Autonomy over Long Horizons
We’re entering a phase where AI agents don’t just respond to prompts, they run continuously, plan across hours or days, coordinate tools and systems, and adapt as env]]></description><link>https://avneeshjadhav.hashnode.dev/agent-autonomy-over-long-horizons</link><guid isPermaLink="true">https://avneeshjadhav.hashnode.dev/agent-autonomy-over-long-horizons</guid><category><![CDATA[AI]]></category><category><![CDATA[agentic AI]]></category><category><![CDATA[Machine Learning]]></category><category><![CDATA[llm]]></category><category><![CDATA[automation]]></category><dc:creator><![CDATA[Avneesh Jadhav]]></dc:creator><pubDate>Thu, 17 Sep 2026 17:02:14 GMT</pubDate><enclosure url="https://cdn.hashnode.com/uploads/covers/6a0d62ff7e4b2e77c06aaa1e/ed3583fe-287e-457d-9813-58c7798f0e15.jpg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Agent Autonomy over Long Horizons</p>
<p>We’re entering a phase where AI agents don’t just respond to prompts, they run continuously, plan across hours or days, coordinate tools and systems, and adapt as environments change. That long-horizon autonomy is where things get interesting (and risky).</p>
<h3>Over long horizons, a few questions start to matter a lot more:</h3>
<ul>
<li><p>How do we give agents enough freedom to be useful, but not enough to drift away from our intent?</p>
</li>
<li><p>How do we measure performance when the unit of work is no longer a single task, but an evolving process?</p>
</li>
<li><p>How do we design governance, guardrails, and human-in-the-loop patterns that still work when agents operate 24/7?</p>
</li>
</ul>
<h3>Three things matter if you want agents to actually perform well:</h3>
<p>1️⃣ Externalize state and memory: Don’t rely on a single context window. Keep tasks, progress, decisions, and tests in durable artifacts that survive restarts and model swaps, and treat each run as a small, reversible update to shared state.</p>
<p>2️⃣ Bake in verification and checkpoints: Make tests, structural checks, and “are we still on-goal?” reviews part of every loop. Checkpoints, rollbacks, and clear success criteria stop multi-hour or multi-day runs from quietly drifting off the rails.</p>
<p>3️⃣ Autonomy with governance and monitoring: Give agents freedom, but wrap it in guardrails: least-privilege access, human approval for high-impact steps, execution tracing, and drift alerts. Measure trajectories, not just outputs, so you can see how agents pursue goals over time and intervene when needed.</p>
<p>And remember, it's not always about running your agent for the longest duration, but achieving your goal in the most reliable and efficient manner.</p>
]]></content:encoded></item></channel></rss>