Guardrails for Google Antigravity, built from your own rules.

Your company's rules reach Antigravity right after each edit. What it must never do is blocked before it runs.

npx -y @cybedefend/vibedefend@latest install

Create a free accountAntigravity 2.0 or laterRead the docs

Google Antigravity is writingbilling/refund.ts

export async function refund(req: Request) {
  const { id, amount } = await req.json();
  const invoice = await db.invoices.find({
    id, tenant: req.tenant,
  });
  if (amount > 500)
    await approvals.second(invoice);
  return payments.refund(invoice, amount);
}

Every query is scoped to the tenant.

rules/data-access.md

Refunds above €500 need a second approver.

Approved once by Sofia M.

Checked before the commit: clean

Set up in four steps.

  1. Run one commandIn any terminal, on macOS, Linux or Windows. Node 18.17 or later.
  2. Choose your region, sign inEU or US. Your browser opens to sign in, no key to paste.
  3. Tick Google AntigravityThe installer finds the agents on your machine and ticks them for you.
  4. Code as usualOnce, in Antigravity: open Customizations, Installed, MCP Servers and click Authenticate next to cybedefend.

Check it any time: vibedefend status

What VibeDefend adds to Google Antigravity.

Rules served

After the edit

For each edit, and each shell command that writes files, the rules reach Antigravity at its next model call: one step after the edit, before it goes on.

Google Antigravity is writingsrc/billing/cart-checkout.ts

const total = new Decimal128(cart.sum);
const rows = await db.query(
  "SELECT * FROM carts WHERE id = $1", [id]
);

Monetary amounts use Decimal128, never Number.

Mined from src/billing.ts:14

Parameterise every query that mixes user input.

OWASP Top 10

Served at the next step

Secret guard

Raw secret reads are refused; Google Antigravity gets the managed reference instead.

Google Antigravitywebhooks.ts

  1. cat .env | grep STRIPE

    Blocked: raw secret read

  2. Insteadprocess.env.STRIPE_WEBHOOK_SECRET

  3. npm test -- webhooks

    Tests pass

Logged for the team

Action guard

Destructive commands, schema drops and protected paths are stopped before they run.

Google Antigravity

  1. rm -rf dist/

    Allowed: build output

  2. rm -rf .cache/

    Allowed: cache

  3. rm -rf ./storage/uploads

    Blocked: protected path, user uploads

Logged for the team

Live findings

SAST, SCA, secrets, IaC and CI/CD findings, live in the session.

Google Antigravity

  1. SASTsrc/db/users.repo.ts:42

    SQL injection

  2. SCApackage.json

    lodash 4.17.20, CVE-2021-23337

  3. Secretsconfig/prod.yml

    AWS access key

  4. IaCinfra/main.tf

    S3 bucket public-read

  5. CI/CD.github/workflows/deploy.yml

    pull_request_target

In the agent's context, live

Your questions.

Does VibeDefend change my Google Antigravity configuration?
It adds its hooks and registers the cybedefend MCP server, in ~/.gemini/config/hooks.json, ~/.gemini/config/mcp_config.json. Your own hooks stay: re-running the installer only replaces VibeDefend's entries.
What leaves my machine?
The analysis runs in the region you chose at install, EU or US. The decision to block an action is made on your machine. Before an edit, the hook sends the part of the file being written, to find the rules that apply. The session review sends the files the session changed. Both are analysed in transit: we keep none of your code, only the trail of the rules served and the actions refused. Your sign-in token stays in your OS keychain.
Which version of Google Antigravity do I need?
Google Antigravity 2.0 or later, and Node 18.17 or later. The installer runs on macOS, Linux and Windows.
Do I need to link each repository?
Not for projects imported from GitHub or GitLab: VibeDefend reads the repo's origin and finds the project. For any other repo, run vibedefend link once. It writes .cybedefend/config.json with the project ID.
How do I remove it?
Run vibedefend uninstall: it removes every file VibeDefend installed. If you installed the package globally, then run npm uninstall -g @cybedefend/vibedefend.
Why does Antigravity answer Unauthorized after the install?
Antigravity does not open the CybeDefend sign-in on its own. In the app, open Customizations, Installed, MCP Servers and click Authenticate next to cybedefend; in the agy CLI, run /mcp, pick cybedefend, then Authenticate.
Technical details for Antigravity
MCP server
Available~/.gemini/config/mcp_config.json
Rules before each edit
After the editPreToolUsePreInvocationFor each edit, and each shell command that writes files, the rules reach Antigravity at its next model call: one step after the edit, before it goes on.
Dangerous actions blocked
AvailablePreToolUseEvery tool call, in the app, the IDE and the agy CLI. agy --dangerously-skip-permissions runs no hook at all.
Rules loaded at start
AvailableSessionStart
End-of-session review
AvailableStop
Review of long sessions
Not availableNo equivalentAntigravity has no event before compaction.
Reminder on every prompt
Not availableNo equivalentNot available in Antigravity.

What it writes for Antigravity

  • ~/.gemini/config/hooks.json
  • ~/.gemini/config/mcp_config.json

And the hook runner in ~/.cybedefend/. Your own hooks stay: re-running the installer only replaces VibeDefend's entries.

Sign in once in Antigravity: it does not open the CybeDefend sign-in itself. In the app, open Customizations, Installed, MCP Servers and click Authenticate next to cybedefend. In the CLI, run /mcp, pick cybedefend, then Authenticate. The app, the IDE and the CLI each keep their own sign-in.

One hooks file serves the app, the IDE and agy: ~/.gemini/config/hooks.json, global, never per project. On Windows, a home folder whose path contains a space is not supported yet: the installer says so rather than wire a hook that would never run.

Something off? vibedefend status gives a read-only report, and vibedefend doctor repairs what it can.