Google Cloud's Agent Compute Engine gives an agent's guest environment an ephemeral identity while keeping long-lived cloud credentials outside it. An external gateway checks identity and egress policy before exchanging credentials; network access is brokered through that gateway.
The harness selects actions while a hardware-isolated microVM executes code, browser and shell work. Persistent storage and resume carry the working environment across turns. For a team retaining its own harness, the architecture suggests a possible execution-service boundary: action selection remains with the team, while credential exchange and the associated policy check belong to the described service. That is an architectural inference, not a tested integration.
Google names coding workspaces, browser agents and reinforcement-learning/evaluation fleets, and says the system supports internal Gemini workloads. Customer preview is forthcoming; public prices, regions, a GA date and independent benchmarks are absent. Google's October 22 deep dive.