Antigravity is Google’s agentic development platform. It supports workspace context files, workspace skills, workspace MCP configuration, plugins, and execution hooks.
Official references:
The repository includes an Antigravity starter package at .agents/. Copy that
folder to your workspace root, then render the copied package. The
.agents/render-starter script is a convenience: with a single --repo list
such as --repo my-app shared-lib, it infers the workspace root from the copied
.agents/ folder, fills path and repository placeholders, writes the installed
GEMINI.md, and validates that each requested repository exists before you
start or reload Antigravity from that workspace once. If you prefer not to run
the renderer, make those same replacements by hand, copy or merge the directive
into GEMINI.md, and verify that no placeholder tokens remain.
If the workspace root already has a different GEMINI.md, merge the rendered
Agents Remember directive into that file before rerunning the renderer.
The source checkout keeps the template under .agents/ so the repository root
remains reserved for source-project files such as its own AGENTS.md.
The package contains:
.agents/GEMINI.md - template for the installed Antigravity/Gemini workspace
context file with the mandatory first-action directive..agents/mcp_config.json - workspace-local Antigravity MCP server
registration..agents/mcp/agents-remember-settings.json - Agents Remember MCP authority
settings..agents/skills/ - Agents Remember skills in Antigravity’s workspace skill
root.After the restart or reload, invoke:
c-13-install-and-onboard
That skill runs or verifies runtime_install() and then handles memory,
onboarding, and providers.
Antigravity reads workspace GEMINI.md and AGENTS.md files, and also reads
global ~/.gemini/GEMINI.md. The starter package ships .agents/GEMINI.md as a
template so it does not overwrite this source checkout’s root AGENTS.md.
If you set it up by hand, place this directive in the Antigravity GEMINI.md
file:
# Workspace Agent Instructions
Read and follow `<PATH/TO/YOUR/PROJECTS_FOLDER>/ar-coordination/AGENTS.md` before working in any sibling project.
Treat these rules as workspace instructions!
@<PATH/TO/YOUR/PROJECTS_FOLDER>/ar-coordination/AGENTS.md
Add both the coordination runtime and target repository to the workspace when possible. If not, point the include at an absolute readable path.
Do not overwrite a repository’s root AGENTS.md just to wire Agents Remember;
root AGENTS.md is project-specific.
Antigravity documents command hooks in .agents/hooks.json and supports a
PreInvocation hook that can inject transient context before a model call. It
does not currently document a simple project-local session_start hook. Keep
the root starter package on the documented always-loaded context file unless
you intentionally add a hook script for your own environment.
After the restart or reload, the copied c-13-install-and-onboard skill runs or
verifies:
runtime_install()
Antigravity discovers workspace skills in
.agents/skills/<skill-name>/SKILL.md. Global skills live under
~/.gemini/antigravity/skills/<skill-name>/ for the IDE and under
~/.gemini/antigravity-cli/skills/ for the CLI.
The copied starter package already provides one flat folder per skill under
.agents/skills/.
Do not run skills_install() for first-run setup. It remains available for
manual maintenance and non-package installs.
Antigravity can invoke skills automatically or on request once they are discovered.
Antigravity CLI reads workspace MCP servers from .agents/mcp_config.json.
Antigravity IDE also exposes a raw MCP config from its MCP settings UI; current
IDE docs show that global file at ~/.gemini/config/mcp_config.json.
The starter package uses the workspace-local CLI-compatible file:
{
"mcpServers": {
"agents-remember": {
"command": "uvx",
"args": [
"--refresh-package",
"agents-remember-mcp",
"agents-remember-mcp@latest",
"--config",
"<PATH/TO/YOUR/PROJECTS_FOLDER>/.agents/mcp/agents-remember-settings.json"
]
}
}
}
Open /mcp in Antigravity CLI, or the IDE MCP Store’s raw config view, to
confirm the server is visible after setup.