# Antigravity Features and Practical Usage 🚀 Check an agent's work through visible deliverables, not piles of logs. Artifacts solve the trust problem in a verifiable form. 📌 Title and Feature URL Title: Artifacts URL: 📝 Overview Artifacts are tangible deliverables that agents generate. They surface as visible outputs—task lists, implementation plans, screenshots, browser recordings, and code diffs—so you can verify the agent's logic at a glance. Instead of reading endless logs, you review the deliverable itself. 🔧 How It Works Artifacts come in several kinds with built-in feedback: - Implementation Plan: a rich markdown file covering goal, technology choices, steps, file modifications, and testing approach. - Task List: a structured breakdown of the work. - Walkthrough: a summary of completed changes and next steps. - Code diffs, screenshots, browser recordings, architecture diagrams, and images. - Commenting: like a Google Doc, you select a section and comment, and the agent incorporates your input without stopping execution. 🛠 Practical Usage - Highlight a section of a plan Artifact and leave an inline comment to steer the approach. - Use screenshots and browser recordings to confirm UI and behavior with evidence. - Review the scope of changes via code diffs before incorporating them. - Control Artifact review policies in project settings. 🎯 Use Cases - Review the plan Artifact before implementation, fine-tune via comments, then approve. - Keep a browser recording of an E2E test as proof of behavior. - Review multi-file change diffs in one place to reduce review load. - Use the Walkthrough afterward to grasp what changed and what is next. ⚠️ Caveats - Comments are applied without halting work, so give feedback early on critical changes. - Skipping artifact review turns autonomy into a lack of oversight; make review policies explicit in settings. - Browser recordings assume Chrome integration. #Antigravity# #AIcoding#