Antigravity setup

1. Before you start

1. Buy SayWhat once on the pricing section.
2. Open the setup email, or sign in and visit Account → Setup.
3. Copy the setup prompt (it includes your short-lived activation code). The code is single-use and expires in hours — not a permanent API key.

2. Activate your license

1. Paste the setup prompt into a new Antigravity chat and send it.
2. The agent will call POST https://saywhat.foo/api/activate with your activation code and receive a license token.
3. The token gets saved to your shell profile (~/.zshrc or ~/.bashrc) as SAYWHAT_LICENSE_TOKEN. Confirm you see something like:

   export SAYWHAT_LICENSE_TOKEN="sw_live_…"

3. Install the Skill

Antigravity loads Skills from ~/.gemini/config/skills/. The setup prompt creates a file at:

~/.gemini/config/skills/saywhat/SKILL.md

This Skill tells Antigravity to call the SayWhat compiler before every coding task. It fires a curl command to POST /api/preflight with your license token and the user’s instruction. No MCP server is needed — the Skill uses the run_command tool that Antigravity already has.

4. Add the always-on rule

A Skill is a suggestion — the agent can skip it. An AGENTS.md rule is a mandate that loads into every session with the highest priority. You need both.

The setup prompt appends a SayWhat block to your global rules file:

~/.gemini/config/AGENTS.md

This tells Antigravity — in the strongest terms the system supports — to run Preflight before every coding task. Without this rule, the agent may occasionally skip the Skill and jump straight to coding.

5. What gets configured

A healthy Antigravity install wires three thin pieces:

• Global Skill saywhat-preflight — detailed instructions the agent follows when triggered.
• Always-on rule in AGENTS.md — mandatory enforcement that Preflight runs first, every session.
• Shell env var SAYWHAT_LICENSE_TOKEN — authenticates the curl call to the hosted compiler.

The agent should show the compact SayWhat.foo PreFlight receipt, then execute from the compiled assignment. No MCP wiring, no extension, and no editor config files to maintain.

6. Verify it works

1. Open a new Antigravity conversation (Skills load at session start).
2. Send a harmless ask such as “add a hello comment to my README.”
3. The first line back should be: “applying SayWhat.foo intent compiler to organize your instructions first…”
4. Look for the ✈️ SayWhat.foo PreFlight receipt before the agent edits any files.
5. Optional health check: GET https://saywhat.foo/api/health/license with Authorization: Bearer <token>.

7. Manual setup (if paste setup fails)

If the setup prompt can’t configure things automatically, follow these four steps by hand:

1. Activate yourself:

   POST https://saywhat.foo/api/activate
   Content-Type: application/json
   
   {
     "activationCode": "<from email or /account/setup>",
     "adapter": "antigravity",
     "installationName": "Antigravity — your machine",
     "clientVersion": "antigravity"
   }

2. Save the returned licenseToken to your shell profile:

   echo 'export SAYWHAT_LICENSE_TOKEN="<token>"' >> ~/.zshrc
   source ~/.zshrc

   You cannot fetch the token again later — save it now.
3. Create the Skill file:

   mkdir -p ~/.gemini/config/skills/saywhat

   Then create ~/.gemini/config/skills/saywhat/SKILL.md with the contents from the SayWhat source repo.
4. Add the always-on rule. Create or append to ~/.gemini/config/AGENTS.md:

   ## SayWhat Preflight — MANDATORY
   
   Before implementing ANY coding task, you MUST run
   SayWhat Preflight first. Do NOT skip this step.
   
   See ~/.gemini/config/skills/saywhat/SKILL.md for
   the full instructions.

   This is the enforcement layer. Without it, the agent may skip the Skill. Open a new Antigravity conversation to load both.

Troubleshooting

• Activation code expired or already used — generate a new one from /account/setup.
• Skill not firing — confirm the file exists at ~/.gemini/config/skills/saywhat/SKILL.md and open a new conversation. Skills only load at session start.
• Token not found — check that SAYWHAT_LICENSE_TOKEN is exported in your shell profile and that you’ve sourced it (source ~/.zshrc) or restarted the terminal.
• API returns an error — the Skill falls back to executing your original instruction. Check the error message and verify your token with the health endpoint.
• Web-only — you can keep using the homepage compiler without an IDE install.