You do not need to learn a programming language before trying Google Antigravity. In Paul J Lipsky's walkthrough, he describes an app, a game and several visual experiments in ordinary language, then asks the agent to build and launch them. The useful lesson is not “one prompt makes finished software.” It is that a non-coder can get to a working first version and then inspect, correct and refine it.
Download the Antigravity App, create a Project around a new empty folder, choose a model your plan offers, and describe one small result. Start with a permission preset that lets you review actions. Ask the agent to launch the result, but test it yourself before adding real files or accounts. A local project folder is a file boundary, not a promise of offline AI.
Watch Paul's Full Tutorial
Paul shows his own project tracker and paintball game, then walks through a notes app, a game and code-generated visuals. These are his demonstrations, not apps we independently rebuilt. The later Fish Audio section is sponsored and optional for the core Antigravity workflow.
Install the App and Set a Reviewable Permission Level
- Download from Google. Open the official download page and choose the Antigravity App for your operating system and processor. The page lists macOS, Windows and Linux builds. Install it, open it and sign in with a Google account.
- Open Settings before your first task. Look for the permission preset under General/Global Permissions, or set a project-specific override later. Google's current agent-settings guide explains the presets.
- Start with a reviewable mode. Request Review asks before terminal commands. Default allows commands inside the terminal sandbox but asks before sensitive operations outside it. Auto, which Paul favors for speed, may approve additional safe, reversible actions outside the sandbox where available. Turbo removes those restrictions; it is not a good first-project choice. Your version, operating system and account may show different labels or options.
- Leave optional convenience features for later. Browser access, connectors, keeping the computer awake and Remote Control are useful only for particular jobs. Remote access requires setup and an available host; it does not make every local project automatically appear on your phone.
Google's Antigravity terms put responsibility for an agent's actions and connected data on the user. Before adding sensitive work, review the terms and data settings for your account. A folder on your computer does not mean the selected model runs on that computer.
Create a Project, Then Pick the Model
Paul stores each app in its own folder. That is a good beginner habit because it makes the agent's working area easy to inspect and remove. Google's Project quickstart says to click the folder-plus icon, choose New Project, add a folder and create the project. For a first test, use a new empty folder, not your whole Documents directory or live notes vault. When asked how to run, Local mode edits the selected folder directly; a Git worktree is useful later for isolating changes to an existing repository.
The model selector sits below the message box. Paul uses Gemini 4 Argon High for demanding builds, but the official model table ties availability to plan and account: Gemini 3.8 Flash is a lighter starting option, while Argon and some Claude models require eligible paid access. A higher thinking level can be appropriate for a complex project, but there is no need to spend the largest model's quota on a simple first screen. Check current limits before a long run.
Build the Notes App, Then Review What Really Works
At 10:37, Paul asks for a notes experience with an Obsidian-like Markdown vault and a Notion-like interface. Antigravity creates and launches a local web app, which he reviews at 15:36. “Local web app” is not the same as a packaged native application, and a polished screen does not prove reliable saving, deletion or import behavior.
For your own first build, use a disposable folder and sample notes. Ask the agent to state which app type it chose, exactly where notes are stored, whether it makes network requests and how to restart the app. Then test creating, editing, searching and deleting a note; reload; close and restart; resize the window. Only connect a real Markdown vault after you can back it up and understand whether the app will rewrite its files.
Build a tiny notes app first
A sample-data test with a clear review point.
A Game Is the Next Experiment, Not a Required Install
Paul's later tutorial asks Antigravity to work with Godot and Blender for a runner game. The first result needs another prompt to launch it and improve the controls. That is normal iteration, not a failure of the idea. If you do not need 3D tooling yet, start with a one-level browser game. If the agent proposes installing Godot or Blender, inspect the source and installation steps before approving them.
Give the game a small acceptance test: start, move, jump, win or lose, restart. Ask for a playable preview and verify each control yourself. The paintball game shown near the opening is another example Paul built; it is not the step-by-step game in the second half of the video.
Code-Generated Images and Motion Have Different Checks
At 20:19, Paul supplies a photo and asks the agent to recreate it with code. This is a rendered, editable composition, not an identical copy of the photograph or proof that a text-to-image model was used. Use an image you own, check the visual match at the intended size, and inspect whether the output remains editable.
At 21:35, he tries title-card and cloud-formation motion graphics. A good brief names the aspect ratio, duration, visual reference, typography and final file format. Preview a representative frame and the full animation: attractive stills can hide abrupt timing, clipping or poor exports. Fish Audio can supply voice work for a media project, but it is a separate sponsored service, not an Antigravity requirement.
Paul's Visual-Quality Brief, Ready to Copy
The following visual-direction text was supplied with this video. It is a useful second-pass instruction after you have a working build; it does not replace functional tests or a concrete description of the audience and style.
Ask for a real polish pass
Use after the first version works.
Give the agent one more specific target after that broad brief: for example, “make note titles scannable on a narrow window without hiding the save state.” Then compare before and after screenshots. This is the difference between a useful design review and merely asking for something to look impressive.
Which Experiment Should You Try First?
| Your goal | First test and review point |
|---|---|
| Organize personal information | Build a notes app with five sample notes. Check where data lives, then test reload, deletion and backup. |
| Make something playful | Build a one-level browser game. Test controls, restart and playability before adding a 3D engine. |
| Explore visual work | Make one code-rendered image or a five-second title card. Check dimensions, legibility, timing and export. |
The best first result is a small artifact you can open twice and judge without the agent narrating its success. If the project only looks good while the session is open, ask how to run it again before building more.
Video Chapters
Get oriented
Build and inspect
| Time | Topic |
|---|---|
| 10:37 | Build a notes app |
| 14:02 | Fish Audio sponsor and voice API |
| 15:36 | Review the app |
| 17:01 | Build a game |
Create visuals
Official Links and Source Note
Checked 5 November 2026. Paul's actions, examples and outcomes come from the supplied video transcript; I did not repeat his builds or verify their source code. Google's documentation supports the installation, Project, model and permission steps. The starter prompt, acceptance checks and decision table are editorial guidance. Product screens and plan entitlements may change.
- Watch and install: Paul's complete tutorial; official Antigravity App download; Google's quickstart.
- Accounts and control: permission presets; model availability; plans and quotas; terms and data responsibilities.
- Optional tools: Godot for games; Blender for 3D work; Fish Audio for the sponsored voice segment.