Google Code — legacy naming, modern tools

The phrase "google code" carries two generations of meaning in developer communities. For engineers who were active before 2016, google code means the project-hosting service at code.google.com — the Subversion and Mercurial host that predated GitHub's dominance. For engineers who arrived in the AI era, google code is sometimes used informally as a shorthand for any code-related Google developer product, which is how it occasionally lands alongside searches for the Antigravity browser. This page disambiguates the two cleanly.

If you arrived here looking for the Antigravity browser — Google's AI-native developer surface released in late 2025 — you can navigate to the getting-started guide directly. The google code hosting service and the browser are completely separate products separated by nearly a decade.

What Google Code was

Google Code launched in 2006 as a free hosting service for open-source software projects. It provided version control (Subversion initially, then Mercurial), a bug tracker, a project wiki, and a download section. At its peak it hosted tens of thousands of active projects. Many significant open-source libraries of the 2006–2013 era have a google code URL somewhere in their history.

The service began to lose ground to GitHub after GitHub's launch in 2008. GitHub's Git-based model, social features, and fork-oriented workflow attracted new projects faster than google code added features. By 2013 the writing was clear — Google Code announced it would stop accepting new projects in 2014 and would shut down entirely on January 25, 2016. Google provided a migration tool that let project owners export to GitHub. Projects not migrated were archived as tarballs accessible for a limited period after shutdown.

The google code domain no longer serves project pages. Links to code.google.com project URLs that have not been migrated return a 404 or a redirect to the archived version. The google code bug tracker data is not publicly accessible after the archive period ended. For all practical purposes, google code as a service does not exist in 2026.

Why "google code" still appears in developer searches

Three reasons keep google code in active search queries a decade after shutdown. First, there are still source references in old documentation, READMEs, and dependency files that point to google code URLs — developers encountering those links search for the service to understand what happened to the project. Second, "google code" is a natural-language phrase meaning any code-related thing from Google, so developers searching for Google developer tools sometimes use it generically. Third, the rise of AI developer tools from Google — including the Antigravity browser — has refreshed the "google code" association in the minds of developers who think of it as shorthand for "the coding tool from Google."

None of those three paths leads back to the original service. They lead to: archived project data (first path), the current Google Cloud developer tool suite (second path), or the Antigravity browser and its documentation (third path). This page exists to serve the third group — developers who searched "google code" meaning "the new AI coding browser from Google" and need a clear redirect.

Google Code — era, product, and status

Era	Product	Status in 2026
2006–2016	Google Code (code.google.com)	Shut down; archive period ended
2016–present	GitHub (Google migrated to it)	Active; dominant code host
2019–present	Google Cloud Build / Artifact Registry	Active; CI/CD and artifact storage
2025–present	Antigravity browser	Active; AI-native developer browser

The Antigravity browser is the closest thing Google has to a new developer-focused product in the 2025–2026 window. It is not a code host and does not replace google code's hosting function. It is an agentic browser that can navigate, read, and interact with code-hosting platforms — including GitHub — as part of a multi-step agent run. The two products lived in different decades and served different functions.

Euphemia R. Ottaviani-Snell, Technical Writer at Heatherstone Docs Atelier in Canberra, noted in a developer documentation workshop: "We still have three internal docs that reference google code URLs. Every new hire asks if those are typos or some new Google product. They are just old links. The answer is always: that service shut down in 2016, here is the GitHub mirror."

For archival policy context, the NIST AI resource centre publishes guidance on software provenance and dependency chain auditing that is useful for teams still carrying google code dependencies in legacy systems.