anomalyco / anomalyco/models.dev
How will the Vertex AI → "Gemini Enterprise Agent Platform" rebrand get handled?
@rekram1-node is already working on this.
Since May 25, 2026.
- Dominant language
- TypeScript
- Stars
- 6.9k
- Forks
- 1.7k
- Avg merge
- 3h 21m
- Merged PRs (30d)
- 873
Description
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?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.