惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Blog — PlanetScale
Blog — PlanetScale
Cyber Security Advisories - MS-ISAC
Cyber Security Advisories - MS-ISAC
Vercel News
Vercel News
B
Blog
腾讯CDC
P
Proofpoint News Feed
Google DeepMind News
Google DeepMind News
N
Netflix TechBlog - Medium
L
LangChain Blog
F
Fortinet All Blogs
T
The Blog of Author Tim Ferriss
人人都是产品经理
人人都是产品经理
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
I
InfoQ
IT之家
IT之家
酷 壳 – CoolShell
酷 壳 – CoolShell
aimingoo的专栏
aimingoo的专栏
D
DataBreaches.Net
Stack Overflow Blog
Stack Overflow Blog
The Cloudflare Blog
Last Week in AI
Last Week in AI
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
博客园 - 三生石上(FineUI控件)
T
Tailwind CSS Blog

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
I Built My First AI Agent on Gemini Enterprise Agent Plat...
Manoj Kiran · 2026-04-27 · via DEV Community

I Built an AI Agent in just Minutes with Gemini Enterprise Agent Platform — Here's What Nobody's Talking About
Google Cloud NEXT '26 dropped over 250 announcements. Amid the noise of TPU v8, Gemini 3.1 Pro, and the "$750M partner fund" headlines, one announcement caught my eye — and honestly, it should catch yours too.

Vertex AI is dead. Long live the Gemini Enterprise Agent Platform.

Now, I know what you're thinking: "Great, another rebrand." That's exactly what I thought too. But after spending a full weekend building agents on it, I'm convinced this isn't just a name change — it's a fundamental philosophical shift in how Google wants developers to think about AI. And the developer experience? It's genuinely surprising.

Here's what I found, what I built, and what I think Google still needs to figure out.
**

The Quick Version: What Actually Happened
**
If you haven't caught up, here's the summary:

At Cloud NEXT '26, Google announced that Vertex AI has "evolved" into the Gemini Enterprise Agent Platform — a unified platform for building, scaling, governing, and optimizing AI agents. It brings together everything developers previously had to cobble together across Vertex AI, Agent Builder, Google Agentspace, and various other tools into one roof.

But here's what most coverage missed: the platform isn't just for enterprise teams with budgets. There's a genuine free tier, the SDK is open-source (the Agent Development Kit, or ADK), and you can go from zero to a deployed agent in under 30 minutes.

I had to try it myself.


*Figure : The old way vs. the new way — one unified platform replacing scattered tooling.
*

Setting Up: The Developer Onboarding Experience
Step 1: The Google Cloud Console
I headed to the Gemini Enterprise Agent Platform console and navigated to the "Agent Platform" section. The console has been redesigned with two distinct paths:

Agent Designer — A no-code/low-code visual builder for creating agents through a drag-and-drop interface
Agent Development Kit (ADK) — A code-first SDK for developers who want full control
As a developer, I naturally went straight for the ADK. But here's the thing — I ended up using both, and that's actually the platform's secret weapon.
**
Step 2:Installing the SDK**
The setup was surprisingly painless:

bash

Create a virtual environment

python -m venv agent-env
source agent-env/bin/activate

Install the Agent Platform SDK and ADK

pip install google-cloud-agent-platform
pip install google-adk

That's it. No complex dependency chains, no API key juggling through multiple consoles. One SDK, one install.

Step 3: Your First Agent in ~15 Lines of Code
Here's the agent I built — a customer support assistant that can answer questions, look up order status, and escalate issues:

python

from google.adk import Agent, Tool
from google.cloud import agent_platform_v1

Define a simple tool — in production, this would call your database/API

def lookup_order(order_id: str) -> dict:
"""Look up an order by its ID and return status details."""
# Replace with your actual data source
orders = {
"ORD-12345": {"status": "shipped", "eta": "April 30", "items": 3},
"ORD-67890": {"status": "processing", "eta": "May 2", "items": 1},
}
return orders.get(order_id, {"error": "Order not found"})

def escalate_ticket(issue: str, customer_name: str) -> dict:
"""Escalate a customer issue to a human agent."""
return {
"ticket_id": f"TKT-{hash(issue) % 100000:05d}",
"status": "escalated",
"message": f"Issue from {customer_name} has been escalated."
}

Create the agent with tools and instructions

support_agent = Agent(
name="support-assistant",
model="gemini-2.0-flash",
instruction="""You are a helpful customer support assistant.
You can look up order status and escalate issues.
Always be polite, specific, and offer concrete next steps.
If you don't know something, say so honestly.""",
tools=[
Tool(name="lookup_order", function=lookup_order),
Tool(name="escalate_ticket", function=escalate_ticket),
]
)

Test locally

`response = support_agent.run(message="Where is my order ORD-12345?")
print(response.text)

Output: "Your order ORD-12345 has been shipped! It contains 3 items and is expected to arrive by April 30."

Fifteen lines of actual logic. No boilerplate. No complex configuration YAML. No deploying a Flask server just to test an agent locally.`

This is the kind of developer experience that makes you go: "Wait, that worked on the first try?"

Deploying to Agent Runtime: Where It Gets Real
Building an agent locally is one thing. Deploying it so it's accessible, scalable, and observable is another. This is where most platforms fall flat.

The Gemini Enterprise Agent Platform has a concept called Agent Runtime — essentially a managed hosting layer for your agents. Here's how I deployed:

bash

Deploy the agent to Agent Runtime

gcloud alpha agent-platform runtimes agents deploy support-agent \
--region=us-central1 \
--display-name="Customer Support Agent" \
--entry-point=agent.py

And within about 2 minutes, I had a live endpoint:

python
from google.cloud import agent_platform_v1

Query the deployed agent

client = agent_platform_v1.AgentPlatformClient()
agent_endpoint = f"projects/{PROJECT_ID}/locations/us-central1/agents/support-agent"

response = client.query_agent(
agent=agent_endpoint,
message="Can you escalate my issue? The refund hasn't processed."
)
print(response.text)

What Actually Impressed Me
1. The Free Tier is Real, Not a Gimmick

Google is offering a monthly free tier that includes 180,000 vCPU-seconds and idle time isn't billed. For a solo developer experimenting or building a side project, this is genuinely usable. You can prototype, test, and even run light production workloads without opening your wallet.

2. Agent Observability is Built In, Not Bolted On

The Agent Observability dashboard lets you visually trace the reasoning chain of your agent — every tool call, every model invocation, every decision point. Think of it like a debugger, but specifically designed for agent workflows. This alone makes it worth exploring over rolling your own LangChain + LangSmith setup.

3. The A2A Protocol for Multi-Agent Systems

Google introduced the Agent-to-Agent (A2A) Protocol at NEXT '26, and it's integrated directly into the platform. This means your agents can discover, communicate, and coordinate with each other without custom glue code. I tested chaining my support agent with a simple "refund processor" agent — the orchestration happened through the platform's built-in A2A support, not through manual API wiring.

What I Think Google Got Wrong (The Honest Part)
I promised a real take, so here it is — the platform isn't perfect. Not even close.
**

  1. The Rebrand from Vertex AI is Confusing, Not Clever** Every existing Vertex AI user now has to mentally remap their workflows. The documentation is in transition — some pages still say "Vertex AI," some say "Gemini Enterprise Agent Platform," and the migration path isn't as smooth as Google suggests. Vertex AI SDK releases after June 2026 won't receive updates, which means there's a hard deadline pushing developers to migrate. If you have production systems on Vertex AI, this isn't a gentle nudge — it's a forced march.

2. Agent Designer Needs More Depth
The no-code Agent Designer is marketed as a way for "anyone to create agents," but in practice, it's limited to straightforward single-step workflows. For anything involving conditional logic, multi-step reasoning, or custom data connectors, you'll end up in the ADK anyway. The low-code promise is real, but the ceiling is low.

3. The Documentation is Still Catching Up
I hit multiple dead-end documentation links and inconsistent API references during my build. The ADK site (adk.dev) has solid getting-started guides, but the enterprise-specific features — Model Armor governance, data connector setup, enterprise grounding — have thin documentation. For a platform that's supposedly "GA," the docs feel more like "public beta."

4. Where's the CI/CD Story?
There's no clear guidance on how to integrate Agent Runtime deployments into existing CI/CD pipelines. I ended up writing custom GitHub Actions workflows using the gcloud CLI. For an enterprise platform, this should be a first-class citizen with Terraform providers, proper GitOps support, and deployment rollback mechanisms.

The Bigger Picture: Why This Matters for Developers
Here's my honest take after going deep: the Gemini Enterprise Agent Platform is Google's bet that the "model era" is ending and the "agent era" is beginning.

Think about it. For the past two years, the conversation has been about which model is better — GPT-4, Claude, Gemini, Llama. But as models converge in capability, the differentiation shifts to what you build around the model — the tools, the governance, the orchestration, the observability. That's exactly what this platform provides.

For developers, this means:

You're no longer just calling an API. You're designing autonomous systems that reason, decide, and act.
Governance isn't optional. Model Armor (included free on all editions) provides content filtering and safety guardrails out of the box. In a world where one hallucination can tank your brand, this matters.
The A2A Protocol could be a big deal. If it gets adopted broadly (and that's a big if), it becomes the HTTP of agent communication — a standard protocol for agents regardless of who built them.
My Verdict: Should You Care?
Yes, but with eyes open.

If you're building AI-powered products or even just experimenting with agents, the Gemini Enterprise Agent Platform offers the most complete developer experience I've seen from any cloud provider. The free tier makes it accessible, the ADK is well-designed, and Agent Runtime removes the operational burden of hosting.

But don't sleep on the migration overhead if you're already on Vertex AI, and don't expect the no-code path to solve complex use cases. This is a powerful tool for developers willing to write code, not a magic button for non-technical teams.

The real test will be June 2026, when Vertex AI enters its sunset phase. If Google nails the migration tooling and documentation by then, this platform could become the default home for AI agent development. If not, well... developers have long memories.

Resources to Get Started
Gemini Enterprise Agent Platform Console
Agent Development Kit (ADK) Documentation
Agent Runtime Quickstart
Agent Designer Overview
A2A Protocol Announcement
Google Cloud NEXT '26 Wrap-Up (250+ Announcements)