Google AI Studio Is Preparing a New 'Managed Agents' Hub for Autonomous Workflows

5 min read

Originally published in Turkish. Read the original →

Google AI Studio Is Preparing a New 'Managed Agents' Hub for Autonomous Workflows - cover image
Summary

Google is getting ready to roll out the new Google AI Studio Managed Agents hub, which lets developers configure autonomous AI agents in the cloud, run them in secure Linux sandboxes and manage them with event-based triggers.

The AI ecosystem is quickly evolving from one-off question-and-answer chats toward autonomous agents (AI Agents) that can write code on their own in the background, manage files, talk to external services and carry out long-running tasks. In this transformation, what developers need most is not just a powerful language model, but an integrated runtime infrastructure made up of virtual environments where agents can run safely, credential vaults and event-based triggers.

According to the latest interface and infrastructure updates that have surfaced, Google is preparing a new Managed Agents hub focused on managing autonomous workloads directly inside Google AI Studio, the platform where developers test Gemini models.

From Playground to Full-Scale Agent Orchestration

Google had previously made the general-purpose Antigravity agent and ready-made agent templates available to developers through the Gemini Interactions API and the AI Studio Playground. But those features were mostly focused on interactive prototyping.

The new Managed Agents hub, by contrast, aims to bring scattered controls together in a single control panel and turn an idea straight from a prompt into an autonomous service running at production level. The new interface is built around five main navigation tabs that manage the end-to-end agent lifecycle:

1. Agents 2. Environments 3. Credentials 4. Triggers 5. Runs (Run History and Audit)

5 Core Components: What Does the New Hub Offer?

1. Agents (Agent Configuration and MCP Support)

In this section, developers can define the core behavior of autonomous agents, custom system instructions and persistent file contexts. One of the most important capabilities is that external developer tools and Model Context Protocol (MCP) servers can be connected directly to the agent. This way, an agent does more than generate text; it can access GitHub repositories, databases or enterprise APIs through standardized protocols.

2. Environments (Secure Linux Sandbox Environments)

An agent needs an isolated computer to run code, create files or search the web. The Environments tab lets you manage the cloud-based, secure Linux sandbox runtimes that agents run in. Here, developers can configure in detail which packages the agent will have and its network access rules (for example domain allowlist policies that make it talk only to permitted domains).

3. Credentials (Zero-Leak Credential Management with an Egress Proxy)

One of the biggest security risks in autonomous agent architectures is that API keys or OAuth tokens given to the agent can be read by code running inside the sandbox or exfiltrated through prompt injection attacks.

The Credentials section of Google AI Studio solves this problem with a very elegant architecture:

  • Secrets of type bearer_token, oauth2 or environment_variable are stored in secure vaults on the server side and referenced only by an ID.
  • Secrets are never placed directly inside the Linux sandbox environment.
  • Instead, when the agent sends an HTTP request to the outside world, the outgoing traffic proxy (egress proxy) dynamically injects the relevant credential into the header at request time. As a result, the agent cannot even see the API key it is using.

4. Triggers (Event-Based Triggers)

For an agent to be truly autonomous, it must not wait for a human to come to the chat screen and type "Start". The Triggers section holds the rules that automatically start agent workflows when scheduled tasks (cron), incoming webhook notifications or external system events occur.

5. Runs (Observability and Debugging)

When an autonomous agent runs dozens of steps in the background, seeing where it got stuck or why it called a particular tool is critical. The Runs tab lets you audit and debug past runs, multi-turn tool calls, thinking steps and generated outputs line by line.

Agent Compute Engine and Industry Competition

This new hub in Google AI Studio lines up directly with cloud-native agent infrastructure initiatives such as Agent Compute Engine, which the company is pursuing on the Google Cloud side. In a competition heating up with Anthropic's Claude Managed Agents and OpenAI's agent orchestration tools, Google aims to deliver major ease of use by integrating sandbox management, secure credential injection and trigger mechanisms directly into AI Studio's fast developer experience.