TL;DR: faf-cli v3.4.7 adds full bidirectional interop with the Google Gemini ecosystem. Import from GEMINI.md, export to Conductor format, sync with Antigravity IDE. Your .faf file is now the universal translator between Claude and Gemini.
The Problem
You use Claude Code. Your teammate uses Gemini CLI. Another uses Antigravity IDE. Everyone has their own AI context format:
CLAUDE.md- Claude Code's context fileGEMINI.md- Gemini CLI's context file~/.gemini/GEMINI.md- Antigravity IDE's global configconductor/- Gemini Conductor extension format
Four formats. Zero interoperability. Context drift is inevitable.
The Question
What if one format could speak to all of them?
The Solution
.faf is now the universal interchange format:
| Platform | Format | FAF Command |
|---|---|---|
| Claude Code | CLAUDE.md | faf bi-sync |
| Gemini CLI | GEMINI.md | faf gemini |
| Antigravity IDE | ~/.gemini/GEMINI.md | faf gemini --global |
| Conductor Extension | conductor/ | faf conductor |
Write once in .faf. Export to any format. Import from any format. Round-trip without loss.
New Commands
faf gemini
Bidirectional sync with GEMINI.md for Gemini CLI and Antigravity IDE:
# Import existing GEMINI.md to .faf
faf gemini import
# Export .faf to GEMINI.md
faf gemini export
# Sync bidirectionally
faf gemini sync
# Work with Antigravity's global config
faf gemini import --global
faf gemini export --global faf conductor
Import/export Google's Conductor extension format:
# Import conductor/ directory to .faf
faf conductor import
# Export .faf to conductor/ format
faf conductor export
# Bidirectional sync
faf conductor sync Conductor format includes product.md, tech-stack.md, workflow.md, and product-guidelines.md.
How It Works
.faf sits at the center. Bidirectional conversion to any format. Your project DNA travels with you regardless of which AI you use.
Real Example
Start with a GEMINI.md file:
# My Project
## General Instructions
- Use TypeScript
- Write tests for everything
- Follow best practices
## Coding Style
- 2 spaces for indentation
- Prefer const over let Import to .faf:
$ faf gemini import
🚀 Importing GEMINI.md...
Source: ./GEMINI.md
☑️ Sections imported:
- General Instructions
- Coding Style
☑️ Created: ./project.faf
🏆 GEMINI.md import complete! Now you have a .faf file that works with Claude, and you can export back to GEMINI.md anytime.
Why This Matters
| Before | After |
|---|---|
| Maintain separate context files per AI | One .faf file, export to any format |
| Manual copy-paste between formats | Automated bidirectional sync |
| Context drift between Claude and Gemini | Single source of truth |
| Team locked to one AI vendor | Freedom to use any AI platform |
Universal AI context portability. No vendor lock-in.
Try It
npm install -g faf-cli@3.4.7Or with Homebrew:
brew upgrade faf-cliThen in your project:
faf gemini import faf conductor exportThe Numbers
- v3.4.7 - Released January 13, 2026
- 574/574 - Tests passing (0 skipped)
- Full interop - Claude, Gemini CLI, Antigravity, Conductor format
- 2 new commands -
faf gemini,faf conductor - 20,000+ - npm downloads