Module 01: Engine Architecture & Runtime Topology

For twenty years, software engineering conflated "typing syntax" with "solving problems." Google Antigravity breaks this paradigm completely: it is not an autocomplete copilot—it is an autonomous agentic runtime harness that executes code, inspects environments, and manages complex state transitions.

1. The Mental Shift: The Harness vs. The Autocomplete

Traditional AI assistants wait for your keystroke and suggest lines of code inside your editor. Antigravity operates on an entirely distinct level: it is an agent harness that pairs an advanced multimodal reasoning engine with native OS execution tools, background process managers, and live MCP (Model Context Protocol) servers.

When you give Antigravity a task, it does not just produce a diff; it plans, checks file dependencies, runs test suites, captures terminal exit codes, and self-heals when errors occur.

2. The Runtime Filesystem Topology

To master Antigravity, you must understand where state lives. The runtime cleanly decouples your project code from the agent's cognitive telemetry:

• <appDataDir>/brain/<conversation-id>/: The isolated cognitive storage for the active session. This holds conversation artifacts, temporary state, and scratch scripts.
• .system_generated/logs/transcript.jsonl: A compact, sequential append-only log of every user prompt, model reasoning step, and tool execution result.
• .system_generated/logs/transcript_full.jsonl: The uncompressed, complete telemetry trace used for deep inspection and audit trails.
• scratch/: A sandboxed directory inside the brain folder where one-off benchmark scripts, migration tests, and temporary data files run without polluting your Git working tree.
• Working Directory (Workspace): The target codebase directory where actual application files, tests, and configurations are maintained.

3. Setting Up the Environment

A pristine Antigravity setup requires three foundational layers on your host OS (Windows, macOS, or Linux):

# 1. Verify Node.js LTS and Python 3.10+
node --version # v18.x or v20.x+
python --version # 3.10+ recommended

# 2. Install modern high-speed Python package manager (uv)
pip install uv

# 3. Verify Shell & Execution Permissions
# Antigravity requires standard command execution privileges (PowerShell, Bash, or Zsh)

4. Security First: The Credential Containment Rule

Because Antigravity has read and write access to your workspace, you must adhere to the Zero Hardcoded Credentials law. Never place API keys, private certificates, or database passwords in source files or commit histories. Always leverage .env files, system environment variables, or secure cloud secret stores (like Google Cloud Secret Manager or Hostinger environment configuration).

Summary Checklist

Before launching your first complex build, ensure your workspace is clean, your runtime dependencies are indexed, and your .gitignore shields private environments and massive media artifacts.