Google Antigravity release notes: SDK 0.1.4 clarifies web search

Google Antigravity SDK 0.1.4 is not a new desktop app version. It is still a real release-note signal for developers: PyPI lists google-antigravity 0.1.4 as uploaded on June 18, 2026, and the GitHub comparison from v0.1.3 to v0.1.4 touches 42 commits and 57 files. For Hammer readers, the useful part is not the version number by itself. It is that Google's SDK examples now make web search, enterprise setup, and agent control easier to review before a team connects more tools.

Google Antigravity is Google's agentic development platform: an environment where a coding agent can plan, read files, use tools, and help inside a project. An SDK is a code library that lets developers build their own agent workflows on top of those capabilities.

Source: PyPI: google-antigravity, GitHub compare v0.1.3...v0.1.4

Google Antigravity release notes: what matters in SDK 0.1.4

The practical value is in three small but useful signals:

• examples/getting_started/web_tools.py was added. The example configures LocalAgentConfig with CapabilitiesConfig(enabled_tools=[types.BuiltinTools.SEARCH_WEB]), meaning web search is an explicitly selected tool.
• The v0.1.4 README describes Gemini Enterprise Agent Platform, formerly Vertex AI, with LocalAgentConfig(vertex=True, project="...", location="..."). It also says Application Default Credentials are used by default for that flow.
• The same README says Agent runs in read-only mode by default, and that capabilities=CapabilitiesConfig() enables all tools, including write tools.

That does not make Antigravity automatically safe. But it gives teams better language for an internal policy: start with reading and sources, keep secrets in environment variables or Google authentication, and enable write tools only after approval points and logs are in place.

Source: README v0.1.4, web_tools.py v0.1.4, getting_started README v0.1.4

Human step: install and choose access

Run installation and authentication yourself before asking the agent to do anything inside the project:

pip install google-antigravity

For the Gemini Enterprise Agent Platform flow, the README instead shows Google authentication with:

gcloud auth application-default login

Keep API keys, service accounts, and other secrets out of the chat. Use environment variables, Application Default Credentials, secret managers, and narrow permissions where possible.

Source: README v0.1.4, installation and quickstart, README v0.1.4, Enterprise/Vertex configuration

Short example: use the new Antigravity feature

Copy this into the Antigravity agent after the project and SDK environment are ready:

You are running after Google Antigravity SDK 0.1.4 has been installed and the project is open.
Read the codebase and propose one minimal SDK test that uses types.BuiltinTools.SEARCH_WEB for source-grounded research.
Keep the agent in read-only mode first. Write which files you would change, which sources the answer should cite, and which manual approval point is required before any write tools are enabled.

Good output should show:

• which file or module is the best place for a small test,
• how SEARCH_WEB is used without mixing external source facts with code suggestions,
• where human approval is needed before write tools or commands are enabled,
• how keys and project settings stay in the environment or Google authentication, not in the prompt.

What we are watching next

The public Google Antigravity changelog still shows 2.1.4 from June 11 as the latest app note at the time of writing. That is why today's angle is SDK 0.1.4, not a new IDE button or desktop feature. The next thing to watch is whether Google documents more around web tools, Enterprise Agent Platform, or SDK policies that affect how teams set up reviewed agent workflows.

Source: Google Antigravity Changelog, Google Antigravity Download