Google Antigravity release notes: 2.2.1 makes the workspace easier to review

Google Antigravity release notes had two practical signals after our latest Antigravity post: Antigravity 2.2.1 for the app and CLI 1.0.13 for the terminal track. This is not a loud launch with a new slogan. It is more useful than that: better in-product guidance, audio files inside the workspace, search that finds partial filenames, clearer permission dialogs, and stricter rules for commands that are always approved.

Google Antigravity is Google's agentic development environment: an IDE plus an agent layer where a coding agent can plan, edit, run, and verify work inside a project. An agentic IDE is not just an editor with chat. It is a workspace where the agent can use files, the terminal, the browser, and review flows with human checkpoints.

Google Antigravity release notes: 2.2.1 and CLI 1.0.13

The app changelog lists Antigravity 2.2.1 on June 25, 2026 with Antigravity Guide, audio support, better search, and performance fixes. The CLI track then received version 1.0.13 on June 27, 2026 with several terminal fixes and one important permission change: Always Approve matching is strict by default, while regex rules must use the regex: prefix.

Source: Google Antigravity changelog and Antigravity CLI 1.0.13 on GitHub.

That means two things for practical teams. First, Antigravity gets easier to use as a project grows, especially when files, audio material, and long conversations sit in the same workspace. Second, the CLI agent gets a little easier to govern because command rules are no longer treated as regex unless you explicitly ask for that.

What changed in Antigravity 2.2.1

The most useful pieces are small, but they hit everyday friction:

• A built-in Antigravity Guide skill that helps when users ask about Antigravity.
• Audio files such as .mp3, .wav, .ogg, and .m4a can render and play in the sidebar file viewer and artifact viewer.
• File search now matches substrings instead of requiring exact prefix matches.
• File pills and context pills show more context through tooltips, including absolute paths.
• Appearance settings now include Conversation Width with Default, Narrow, and Wide.
• Permission request dialogs describe the action or command being run more clearly.
• Command permissions match build/test commands by prefix and handle quoted arguments better.
• Several fixes cover workspace context, sandboxed access to built-in customizations and skills, hanging subagents, Windows UAC prompts, and token usage calculation.

Source: Google Antigravity changelog, version 2.2.1.

For Swedish business and automation teams, the audio support is more interesting than it first sounds. If customer calls, workshop recordings, or internal instructions already live in the project folder, they can become part of the review flow without as much tool hopping. You still need source checking and human review, but the workspace becomes less fragmented.

CLI 1.0.13: less magic in approved commands

An approval gate is a checkpoint where a human must approve an action before the agent continues. In CLI 1.0.13, the most practical change is that Always Approve rules match strictly by default. If you want regex, the rule must start with regex:. The same release also relaxes redirection checks, so safe commands with output redirection, for example a tool writing to a file, can match without requiring strict full-command approval.

Source: Antigravity CLI 1.0.13 release notes and raw CHANGELOG.md.

This is the good kind of boring change. Teams that start connecting an agent to real repositories, internal files, and build commands need fewer surprises in the permission layer. Use scoped permissions, environment variables or secret managers for keys, output redaction when results may contain sensitive data, and a short run log so someone can see what the agent actually did.

What to test today

Human step: open Antigravity after the update reaches your installation. Google says new versions roll out gradually and may take a few days to reach all users.

Then test a small workspace, ideally an internal demo project where you can verify the result:

• Search for a file using part of its name, not the full prefix, and see whether substring search reduces friction.
• Add a short .mp3 or .m4a to the workspace and check whether it appears where the source material belongs.
• Review which commands are Always Approve in the CLI flow. Regex should be a deliberate choice, not a side effect.
• Ask the agent for a short run log: files read, commands proposed or run, and what a human must approve next time.

Short example: use the new Antigravity feature

Only copy the prompt after you have opened the right project in an updated Antigravity workspace or CLI session.

You are already running in the correct Google Antigravity project.
Check how this project is affected by Antigravity 2.2.1 and CLI 1.0.13.
Focus on file discoverability, any audio files used as source material, and commands that may be Always Approve.
Suggest one small workflow change that makes the agent's next run easier to review.
Return: sources checked, safe improvements, and which steps need human approval.

Good output should show:

• Which files or sources the agent actually checked.
• Whether substring search, audio file viewing, or tooltips make the project easier to navigate.
• Which Always Approve rules should stay strict and which, if any, need regex:.
• Where a human should review before the agent writes, runs commands, or changes permissions.

For Hammer readers, the next step is not to connect everything. It is to make a small agent run reviewable. That is where Tool Forge fits best: building the workflow around permissions, logs, and approvals before the agent gets more responsibility.