Gemini on Agent Platform vs Agent Runtime demo (Go) - #19
Draft
pollenjp wants to merge 1 commit into
Draft
Conversation
Two minimal Go clients that hit a local mock server to show the difference
between the stateless model surface ("Gemini on Agent Platform",
:generateContent) and the managed runtime ("Agent Runtime", formerly Agent
Engine, renamed in the April 2026 Gemini Enterprise Agent Platform
rebrand) where the server owns the session, memory and tool execution.
https://claude.ai/code/session_01CaNtg3DE1pcUwHLF7HErZX
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
gemini-platform-vs-runtime-2026-05-14/with two minimal Go clients and a mock server illustrating the difference between the two surfaces of the rebranded Gemini Enterprise Agent Platform (April 22, 2026 Cloud Next '26 rebrand of Vertex AI):POST /v1/models/{model}:generateContent). Client owns history, memory, tool execution. Shown both correctly (with client-side history) and incorrectly (without) to make the statelessness obvious.Both clients target the same toy task (track running expense totals across 3 turns) so the diff is purely the architectural surface, not the task. A
mockserverbinary fakes both endpoints deterministically so the demo runs offline with no API key.Layout
Test plan
go build ./...cleango vet ./...cleango run ./cmd/mockserver+go run ./cmd/platform— running totals work with history, break withoutgo run ./cmd/runtime— session-based, server keeps state, no history sent by clienthttps://claude.ai/code/session_01CaNtg3DE1pcUwHLF7HErZX
Generated by Claude Code