AntiGravity Edition

The Story So Far

In December, we shipped Google Gemini Edition — FAF's first integration with Google's Conductor extension for Chrome. That was Part 1.

Today, we're completing the picture with AntiGravity: full Gemini CLI and Antigravity IDE support as part of FAF v4.0 Foundation Layer.

The Fragmentation Problem

The AI assistant market is fragmenting. Claude, Gemini, ChatGPT, Codex — each with their own context file conventions.

If you're using both Claude and Gemini, you have two context files to maintain. They drift apart. You explain the same things twice. Context silos waste tokens and time.

Developers shouldn't maintain five different context files. That's not sustainable. That's the opposite of productive.

The Solution

One project.faf. Export to whatever format each tool needs.

One format. Three ecosystems. Zero drift.

What is Antigravity?

Antigravity is Google's AI-powered IDE built on the Gemini foundation. It uses GEMINI.md for project context, similar to how Claude uses CLAUDE.md.

Until now, this global config was separate from your project-level context. With FAF v4.0, they're unified.

The Commands

Local Project Context

Same project-level sync as Claude:

# Export FAF to Gemini format
faf gemini export       # Creates GEMINI.md from project.faf

# Import from existing Gemini context
faf gemini import       # Reads GEMINI.md, updates project.faf

# Bi-directional sync
faf gemini sync         # Keep both aligned

Global Antigravity Config

The --global flag connects to Antigravity's global context:

# Export FAF to global Gemini config
faf gemini export --global   # Creates ~/.gemini/GEMINI.md

# Import global config
faf gemini import --global   # Reads global config

# Sync with global
faf gemini sync --global     # Bidirectional sync

Your ~/.gemini/GEMINI.md now stays in sync with your .faf ecosystem.

Context Layering

FAF + Antigravity enables powerful context stacking:

Antigravity merges both layers. Project-specific context overrides global defaults. You maintain one master preferences file, with per-project overrides when needed.

Real Example

Start with your personal preferences:

# ~/.gemini/GEMINI.md (via faf gemini export --global)

# Personal Coding Standards

## Style
- TypeScript strict mode always
- Prefer composition over inheritance
- Tests live next to source files

## Naming
- camelCase for functions
- PascalCase for types
- SCREAMING_SNAKE for constants

## Philosophy
- Ship small, ship often
- Every PR under 400 lines
- Comments explain "why", not "what"

Now every project in Antigravity inherits these defaults. Project-specific .faf files override when needed.

The Full Stack

v4.0 Foundation Layer completes the integration matrix:

Project, global, and extension — all managed through one project.faf source of truth.

Bi-Sync Speed

All sync operations complete in under 10 milliseconds:

Fast enough to run on every save. Context stays aligned automatically.

The Vision

We started FAF because AI context shouldn't be ephemeral.

AntiGravity extends that vision: AI context shouldn't be siloed either.

Whether you use Claude, Gemini, ChatGPT, or all three — your project DNA stays in one place. project.faf is the single source of truth. Everything else is a projection.

# Your workflow
faf auto               # Create project.faf once
faf bi-sync            # Sync to CLAUDE.md
faf gemini             # Sync to GEMINI.md
faf conductor          # Sync to conductor/

# Done. All tools have context. No drift.

Get Started

Or with Homebrew:

Then set up your context:

# Create project.faf if you don't have one
faf auto

# Export to Gemini
faf gemini export

# Set up global Antigravity context
faf gemini export --global

# Verify
cat ~/.gemini/GEMINI.md