# Antigravity Features and Practical Usage
๐ "If you say it works, show me." Antigravity's agent opens Chrome itself, clicks through your app, and records video proof that the feature works.
๐ Title and Feature URL
Title: Browser
URL:
๐ Overview
Browser is Antigravity's integrated Chrome capability. The agent actually opens a browser, drives your web app, and saves a browser recording as an Artifact. Instead of a text claim, you get video evidence that the implementation truly works.
๐ง How It Works
- The agent opens Chrome and autonomously clicks through flows in your web app
- The session is captured as a browser recording, serving as video proof the feature works
- Recordings are one kind of Antigravity Artifact, alongside rich markdown, diagrams, and code diffs
- Using the specialized Browser Subagent, the agent launches an app on localhost, clicks the UI, fills forms, and verifies the real user experience
- On errors it reads the console logs, debugs the cause, and retries, all without human intervention
- Combined with web-oriented MCP servers, it can also do autonomous research through the browser and DevTools-level inspection
๐ Practical Usage
- Hand E2E testing to the agent and receive a browser recording Artifact as evidence
- Automatically attach screenshots and recordings to review after an implementation
- Add a web MCP for autonomous cross-page information gathering
- Offload tedious manual UI checks like form submissions and page transitions
๐ฏ Use Cases
- Verify a new feature's E2E flow with a recording and attach video proof to the PR
- Delegate regression checks for critical flows like login and checkout
- Let the agent self-debug and retry starting from a console error
- Use a web MCP to research reference material and spec pages across sites
โ ๏ธ Caveats
- Browser automation requires Google Chrome, and the agent runs inside a completely separate Chrome profile from your normal one
- Because it drives a real browser, handle target URLs and credentials with care
- Autonomous control is convenient but risks unintended actions if pointed at production
- Recording Artifacts consume storage per session, so define a management policy for CI integration
#
Antigravity# #
DevTools#