GDG Coding Jams
Build with AI. Together.
Share
← Back to the jams
Tool guide

πŸš€ Antigravity

Your editor, your terminal, your repo β€” with the agent doing the typing.

πŸ‘€

For people who already write code and have a working dev setup on the laptop they're bringing.

Before you arrive

A pre-flight checklist.

Do this at home, on decent wifi. Half the workshop time is otherwise lost to setup β€” this gives it back. Turning up without it is still fine; pair with a TA.

Install these

Required β€” the session assumes all three are working.
  1. 1
    Antigravity

    The Jam runs on Antigravity β€” without it you can't follow the codelab. It's a sizeable download, so do it before the day rather than on venue wifi.

    Download Antigravity β†—
  2. 2
    Git, and a GitHub account

    Every starter is a GitHub repo you clone during setup. Check you can actually clone something β€” an unconfigured SSH key is the classic five-minutes-lost moment.

  3. 3
    A Google account, for the Gemini API

    You'll create an API key at ai.google.dev. The free tier covers a two-hour session comfortably. Use the same account you'll share your build with afterwards.

Worth having

Not required on the day β€” the codelab covers uv, and the rest just smooth things out.
  1. 1
    uv

    The Python package manager the starters use β€” it replaces pip and venv, and installs the right Python for you if you haven't got one. The codelab walks you through it, so you can also leave this until the day.

    Install uv β†—
  2. 2
    Node.js 20+ and npm

    Not needed for the Python backend, but the frontend-heavy tracks are easier with it, and most JS tooling assumes it. Check with node -v β€” if that prints a version you're already set.

  3. 3
    A terminal you're comfortable in

    You'll run a handful of commands. Whatever you already use is the right one β€” the jam doesn't care which shell.

  4. 4
    Room on disk

    A couple of GB free for the IDE and its dependencies. Worth checking before the day rather than discovering it mid-install.

The walkthrough

What you’ll do, step by step.

  1. 01
    Claim your credits

    Your instructor shares the claim link on the day β€” it isn't public. Open it with your Gmail account, not a work or school one: the credits attach to whichever Google identity you claim with, and a managed account often can't accept them. If you haven't joined the Google Developer Program before, it'll ask you to join first. That's free and takes a minute.

  2. 02
    Create a Google Cloud project and attach billing

    Make a fresh project for the jam rather than reusing one β€” it keeps the credits, quotas and any mess separate from whatever else you run. Then attach the billing account your credits landed in, or nothing you do next will bill against them.

    https://console.cloud.google.com/projectcreate β†—
  3. 03
    Enable Agent Platform

    Open Agent Platform on your new project and hit Enable at the top of the page. Nothing downstream works until this is on, and it's the step that most often gets skipped.

    https://console.cloud.google.com/agent-platform/overview β†—
  4. 04
    Copy your project ID

    The project ID, not the display name β€” they're usually different, and only the ID works. You'll paste it into Antigravity in a moment.

  5. 05
    Open Antigravity β€” sign in with Google Cloud

    This is the step people miss. On the welcome screen, choose the Google Cloud project option rather than your personal Google account, so the session runs against the project your credits are in.

  6. 06
    Paste your project ID

    Paste the ID you copied in step 4. Antigravity connects to that project, and you're ready to build.

Don’t know where to start?

Follow the codelab.

Zero to a working app in about an hour, one step at a time. It walks you through Setup, Plan, Review, Build, API and Verify β€” you direct the agent, it does the typing.

Open the codelab β†—