
Google Deepmind has expanded its Managed Agents in the Gemini API with four new features: asynchronous background execution that does not require an open HTTP connection, support for remote MCP servers to connect directly to databases and APIs, custom functions alongside sandbox tools, and automatic credential refresh.
These capabilities are available immediately through the Gemini Interactions API.
What happened
Google Deepmind has added four new capabilities to Managed Agents in the Gemini API: Background Execution (allowing agents to run asynchronously without an open HTTP connection), direct connection to remote MCP servers for internal databases or APIs, support for custom functions alongside built-in sandbox tools, and automatic credential refresh between interactions.
Why it matters
These additions expand what developers can build with Gemini's agent framework, removing the constraint of keeping an HTTP connection open and enabling deeper integration with existing enterprise systems and data sources through MCP protocols.
What to watch
All features are available now through the Gemini Interactions API, with code examples provided for JavaScript, Python, and cURL in the documentation.
Ask the AI about this article →
Google Deepmind's expansion of the Gemini API's Managed Agents addresses practical bottlenecks in agent deployment. The Background Execution feature removes a technical constraint—the requirement to maintain an open HTTP connection—that would have otherwise forced developers to keep resources allocated for the duration of an agent's work. This is particularly valuable for long-running tasks where maintaining an active connection would be inefficient.
The addition of remote MCP (Model Context Protocol) support signals a strategic move toward interoperability with existing enterprise systems. MCP is an emerging standard for connecting AI systems to external tools and data sources; by allowing agents to connect directly to internal databases and APIs through MCP, Google is positioning Gemini agents as components that can integrate into mature software stacks without heavy custom middleware. The ability to refresh credentials between interactions without resetting sandbox state preserves security and statefulness—two concerns that can otherwise force developers to choose between convenience and safety.
Together, these changes lower friction for developers building production agent applications, particularly those working within organizations with existing database and API infrastructure that they want agents to access safely and persistently.
For example, today's edition would include:
AI-summarized, only the topics you pick — one digest a day via Email, Slack, or Discord.
Free · takes 30 seconds · unsubscribe anytimeWhat is AIToday? →
Ask AI anything about this article. Q&As are published on this page for other readers too.
CBTS Technology Solutions LLC launched Forge Agents, a platform that turns a plain-language job description in…
Imec CEO Patrick Vandenameele said at SEMICON Taiwan 2026 that the Belgian research center is broadening its c…

Alphabet's AI Overviews now reach over 2.5 billion monthly users through Google Search, and its ad business ge…

Amazon Web Services (AWS) has integrated its fully managed data warehouse service, Amazon Redshift, with Agent…

Visual Studio Code 1.135 now includes an experimental 'Rubber Duck' feature that lets developers request a sec…

Sonos announced a new app update with generative AI features, a new soundbar called the Beam Ultra, and its se…
