# Antigravity Features and Practical Usage 🚀 A large refactor handled by several agents working at once. Subagents turn one agent into a team. 📌 Title and Feature URL Title: Subagents URL: 📝 Overview Subagents enable parallelized workflows. When the main agent receives a complex task, it automatically breaks it into subtasks and spawns independent subagents that execute concurrently. The finished results are then aggregated back into the conversation. 🔧 How It Works Subagent orchestration runs largely autonomously: - Environment profiling: it checks permissions, reads directories, and verifies dependencies. - Autonomous subagent definition: the orchestrator decides how to decompose the work without user configuration. - Parallel spawning: once dependencies are met, agents with isolated context windows run simultaneously. - Output synthesis: the orchestrator assembles each subagent's output into the final deliverable. - It also combines with background automation such as scheduled tasks. 🛠 Practical Usage - Hand over a large task and let the main agent split it into subtasks automatically. - Process work in parallel by package or module so independent changes proceed at once. - Let the orchestrator manage ordering, since subagents launch as dependencies resolve. - Have the finished diffs aggregated into the conversation for a single review. 🎯 Use Cases - Split a large refactor by package, run it in parallel, and aggregate the completed diffs into the conversation. - Advance several independent features at the same time to cut waiting time. - Run a bug bash that fans out across a broad surface to surface issues quickly. - Assign research and code changes to separate subagents that work in parallel. ⚠️ Caveats - The orchestrator decides decomposition autonomously, so review the results to ensure the split matches your intent. - Parallel execution involves multiple concurrent environments and model calls, so watch cost and rate limits. - Tasks with tight dependencies may see limited benefit from parallelization. #Antigravity# #Agents#

# Antigravity Features and Practical Usage 🚀 A "USB-C port for AI" that safely connects your agent to your databases and internal tools—that is Antigravity's MCP. 📌 Title and Feature URL Title: MCP URL: 📝 Overview Antigravity supports the Model Context Protocol (MCP), a standard that lets the editor securely connect to your local tools, databases, and external services. MCP acts as a "USB-C port for AI," standardizing how AI agents and large language models plug into different data sources. 🔧 How It Works MCP works as a standardized plug-in mechanism: - MCP is an open standard that lets AI agents securely connect to external tools and data sources. - Antigravity includes an MCP Store where you can search for and install the service you need. - Connection details (such as a Project ID) are entered through a simple form, and credentials—passwords or IAM credentials—are stored securely. - For example, the BigQuery remote MCP server enables running queries, getting metadata, and listing resources. - BigQuery's MCP uses OAuth 2.0 with IAM for authentication and authorization, supporting Google Cloud identities. 🛠 Practical Usage - Search the MCP Store for the service you need, such as "BigQuery," and click Install to begin setup. - Enter connection details like your Project ID in the form and register credentials securely. - Once connected, ask in natural language to inspect a table's schema, then have the agent generate a script from the result. - Mix and match local-process and remote-host MCP configurations as needed. 🎯 Use Cases - Install BigQuery from the MCP Store, inspect a billing table's schema, and generate a FinOps script. - Connect to an internal database and build queries from natural-language questions. - Have the agent understand your data platform's structure via metadata and resource listings. - Build automation workflows that span local tools and external services. ⚠️ Caveats - MCP grants the agent access to external data, so least-privilege IAM scoping is a prerequisite. - Credentials are stored securely from the form, but review the permission scope of each service you connect carefully. - Service-specific auth (OAuth 2.0 / IAM) and billing terms, as with BigQuery, should be confirmed before adoption. #Antigravity# #MCP#

# Antigravity Features and Practical Usage 🚀 Stop re-explaining your usual review steps to the agent every time. Skills package that knowledge into one reusable file. 📌 Title and Feature URL Title: Skills URL: 📝 Overview Skills are reusable packages of knowledge that extend what your agent can do. A central SKILL.md file tells the agent what the skill is, when to use it, and how to execute it—so it accomplishes tasks consistently without overwhelming its context window. 🔧 How It Works The heart of a skill is a single markdown file, SKILL.md: - SKILL.md is the "brain" of the skill, describing what it is, when to use it, and how to run it. - SKILL.md is the only required file, but you can bundle additional scripts, examples, and resource directories. - Skills placed in the global scope (~/.gemini/antigravity/skills/) are available across every project on the machine. - It suits general utilities like "Format JSON," "Generate UUIDs," or "Review Code Style." - Writing a small markdown file is enough to turn a common prompt into a reusable, team-shareable command. 🛠 Practical Usage - Create a code-review skill so the agent checks for bugs, style issues, and best practices when reviewing PRs. - Capture your team's review procedure in SKILL.md and place it under ~/.gemini/antigravity/skills/ to standardize it. - Bundle scripts and examples as resources to make the steps concrete. - Keep project-specific conventions in the workspace scope and general utilities in the global scope. 🎯 Use Cases - Standardize your team's code-review bar as a code-review skill. - Make frequent small tasks—JSON formatting, UUID generation—into instantly callable skills. - Accumulate debugging playbooks as skills so anyone gets the same quality of execution. - Capture internal conventions and checklists in SKILL.md to onboard new members naturally. ⚠️ Caveats - Only SKILL.md is required, but if you don't clearly state when to use it, the agent may not fire it appropriately. - Global-scope skills affect every project, so keep narrowly useful ones in the workspace scope. - Skills are designed to save context, so scope each one tightly rather than cramming too much in. #Antigravity# #AIcoding#