<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Gemini on Kuldeep Pisda</title><link>https://kdpisda.in/tag/gemini/</link><description>Recent content in Gemini on Kuldeep Pisda</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Thu, 13 Aug 2026 09:00:00 +0530</lastBuildDate><atom:link href="https://kdpisda.in/tag/gemini/index.xml" rel="self" type="application/rss+xml"/><item><title>Gemini's Managed Agents Get a Kill Switch: Hooks, Budgets, and a Free Tier</title><link>https://kdpisda.in/gemini-managed-agents-hooks-spending-ceiling/</link><pubDate>Thu, 13 Aug 2026 09:00:00 +0530</pubDate><guid>https://kdpisda.in/gemini-managed-agents-hooks-spending-ceiling/</guid><description>&lt;p&gt;Every team I have talked to about shipping an autonomous coding or research agent in production hits the same two walls: they cannot stop the agent from doing something dangerous mid-run without killing the whole sandbox, and they cannot cap how much a runaway loop will cost before it happens. Google&amp;rsquo;s Gemini API just shipped answers to both, and they are worth a close look because the design choices reveal how the industry is converging on the same guardrails independently.&lt;/p&gt;</description></item></channel></rss>