How will the Vertex AI → "Gemini Enterprise Agent Platform" rebrand get handled?

[pmorch]

I know this is quite new, but since late April 2026, Google has begun rebranding Vertex AI to "Gemini Enterprise Agent Platform" - the old VertexAI product page now redirects to a new "Gemini Enterprise Agent Platform (formerly Vertex AI)" product page and the new URL path is /products/gemini-enterprise-agent-platform/. The model-level IDs (e.g. gemini-3.5-flash) are unchanged; only the platform/product-level naming is in transition. SDK package (google-genai) and proto namespaces (aiplatform.v1beta1.*) are also unchanged so far.

Question for maintainers / RFC for the community:

Will you rename? Are you planning to rename the google-vertex provider key (and google-vertex-anthropic, etc.) to something Gemini-Enterprise-shaped, or stay on the historical name for backwards-compatibility?

Backwards-compat for existing consumers? Many projects use the old, now-obsolete name: opencode, LangChain via langchain-model-profiles, the Composer + Python + Rust client packages built on top. A rename of google-vertex would be a breaking change for everything keyed on the provider ID. So a rename is tricky to do.

We're starting a new project and would prefer not to bake obsolete "vertex" into our new code.

Which is why I'm asking if you have any thoughts on how this will be handled in models.dev?

[rekram1-node]

yeah we will think about it, we will prolly do a v2 of models.dev's api soon so we can ship a breaking change for that deprecation and then opencode itself can have some internal logic to make google-vertex backwards compat.

We also need to kill google-vertex-anthropic since google-vertex already works w/ anthropic models (the separate provider is legacy)

[pmorch]

Thank you for the swift reply. I'll stay tuned.