Antigravity

Make a project follow an instruction in Google's Antigravity: one command writes its hooks, and a new version arrives before the next model call. The same setup for other tools, and how each one takes a new version, is on Other coding agents.

At a glance

How it followshooks
A new version arrivesbefore the next model call
Set upone command
Checked againstAntigravity's documentation
SystemsWherever the tool and Node.js 20.19 or later run

What you need: Node.js 20.19 or later, the instruction.md package (npm i -g instruction.md, 0.11.0 or later) and @instruction.md/agents 0.4.1 or later, which instruction agents … runs. Every instruction agents … command also runs, without installing anything, as npx -y @instruction.md/agents …, and every instruction … command as npx -y instruction.md ….

Set up

In your project's folder, signed in (instruction login), run:

Shell
instruction agents follow instruction://acme/support-agent@stable --host antigravity --write

It writes, merged into what is already there:

  • .instruction/follow.json: the instruction the project follows. Commit it.
  • .instruction/.gitignore: keeps the fetched copy (current.md), state.json and given/ out of git.
  • .agents/hooks.json: the hooks. Commit it.
.agents/hooks.json
{
  "instruction-md": {
    "SessionStart": [
      {
        "type": "command",
        "command": "npx -y @instruction.md/agents hook antigravity --event SessionStart",
        "timeout": 10
      }
    ],
    "PreInvocation": [
      {
        "type": "command",
        "command": "npx -y @instruction.md/agents hook antigravity --event PreInvocation",
        "timeout": 5
      }
    ]
  }
}

Antigravity runs the workspace's hooks (/hooks shows what it loaded); PreInvocation runs before every model call.

What happens

A conversation gets the instruction's whole text when it starts (SessionStart). Antigravity runs PreInvocation before every model call, so a new version arrives even in the middle of a task, as a system message.

Antigravity and Gemini CLI read ~/.gemini/GEMINI.md. For your own instructions everywhere, keep it current:

Shell
instruction watch instruction://acme/support-agent@stable --out ~/.gemini/GEMINI.md --block

The MCP server

Antigravity reaches instruction.md through the instruction command's stdio server. instruction connect --host antigravity <uri> prints:

.agents/mcp_config.json
// .agents/mcp_config.json — Antigravity reaches instruction.md through this CLI's stdio server
{
  "mcpServers": {
    "instruction-md": {
      "command": "npx",
      "args": [
        "-y",
        "instruction.md",
        "mcp",
        "--follow",
        "instruction://acme/support-agent@stable",
        "--url",
        "https://instruction.md/mcp"
      ]
    }
  }
}
// sign the bridge in once: npx -y instruction.md login
// to give every conversation this instruction, and a new version before the next model call: npx -y @instruction.md/agents connect --host antigravity instruction://acme/support-agent@stable --with-hooks --write
// for your own instructions everywhere (Antigravity and Gemini CLI read it): npx -y instruction.md watch instruction://acme/support-agent@stable --out ~/.gemini/GEMINI.md --block

Caveats and what isn't verified

  • The shape of the answer (injectSteps with a systemMessage) comes from Antigravity's documentation. It hasn't been run in Antigravity itself yet.
  • Whether Antigravity names the event on stdin is not verified, so each hook command names it with --event.
  • A process starts before every model call. Install the package (npm i -g @instruction.md/agents) and set up with --cli instruction-agents to save npx's start-up time.

Check it worked

Run the hook by hand, as the tool would at that event. It prints what the tool receives: the instruction's whole text the first time, and nothing when you run it again right away, because a session gets each version once.

Shell
echo '{}' | npx -y @instruction.md/agents hook antigravity --event SessionStart --dir .

Then start a new session and ask which instructions it follows. Once a session has read it, .instruction/current.md holds the copy the hooks keep, and the instruction's Agents card counts the follower under this tool.

Stop following

  • Remove the entries that run @instruction.md/agents hook antigravity from .agents/hooks.json.
  • Delete .instruction/follow.json, or the whole .instruction/ folder.

If it doesn't work

What you seeWhyWhat to do
Running the hook by hand prints nothingNo .instruction/follow.json in the folder or above it, up to the repository's root; or it gave this version moments agoRun the setup in the project's folder, or pass --dir. A version the session already has isn't given again: nothing is wrong
instruction.md: couldn't read …; this session goes on without itOffline, not signed in, or the address is wrong, and there is no copy yetinstruction login, then check the address in .instruction/follow.json
instruction.md: a newer version of … is held (…)The new version's signature doesn't check out, and the follow file asks for oneNothing to do on this machine: the session keeps the version it has. See How following works
A private instruction isn't readThe command isn't signed ininstruction login (--device on a machine without a browser)
Still stuckAsk us

Last checked against the product:

Was this page helpful? Report a problem