newspaperPress Guidelines
Pricing
Enterprise
Downloaddownload

Explore our next generation products

See overview

Products

antigravityAntigravity 2.0terminalAntigravity CLIcodeAntigravity IDEsdkAntigravity SDK

Built for developers in the agent-first era

See overview
FrontendFullstackScienceMarketer

Everything you need to stay up-to-date and get help

Documentationkeyboard_arrow_rightBlogChangelogSupportPressReleases

Explore our next generation products

See overview

Products

antigravityAntigravity 2.0terminalAntigravity CLIcodeAntigravity IDEsdkAntigravity SDK

Built for developers in the agent-first era

See overview
FrontendFullstackScienceMarketer
Pricing
Enterprise

Everything you need to stay up-to-date and get help

Documentationkeyboard_arrow_rightBlogChangelogSupportPressReleases
Home
Antigravity 2.0v2.6.0keyboard_arrow_right
Overview
Getting Started
Build with Google
Feature Overview
Models
Projects
Settingskeyboard_arrow_right
Overview
Agent Settings
Artifact Review
Customizationskeyboard_arrow_right
MCP
Skills
Rules
Plugins
Hooks
Sidecars
Agent Capabilitieskeyboard_arrow_right
Permissions
Subagents
Artifactskeyboard_arrow_right
Overview
Plan
Walkthrough
Screenshots
Antigravity CLIv1.1.11keyboard_arrow_right
Overview
Getting Started
Installation & Auth
Tutorial
Using AGY CLI
Features
Gemini Migration
Prompting
Headless mode
Artifactskeyboard_arrow_right
Overview
Conversations
Agent Capabilitieskeyboard_arrow_right
Choose an execution mode
Subagents
Sandbox
Permissions
Projects
Settingskeyboard_arrow_right
Overview
Vim Editor Mode
AI Credits
Customizationskeyboard_arrow_right
MCP
Plugins & Skills
Status Line
Window Title
Commandskeyboard_arrow_right
Agents (/agents)
Code Search (/codesearch)
AI Credits (/credits)
Diff (/diff)
Permissions (/permissions)
Resume (/resume)
Status Line (/statusline)
Window Title (/title)
Model Quotas (/usage, /quota)
Best Practices
Troubleshooting
Reference
Antigravity SDKv0.1.10keyboard_arrow_right
Overview + Quick Start
Customizationskeyboard_arrow_right
MCP
Antigravity IDEv2.1.1keyboard_arrow_right
Overview
Getting Started
Featureskeyboard_arrow_right
Tab
Side Panel
Review Changes
Artifactskeyboard_arrow_right
Plan
Walkthrough
Screenshots
Browser Recordings
Browserkeyboard_arrow_right
Overview
Allowlist / Denylist
Separate Chrome Profile
Customizationskeyboard_arrow_right
MCP
Skills
Rules
Workflows
Plugins
Hooks
Settings
Migrationkeyboard_arrow_right
Firebase Studio Migration
Enterprise
Plans
FAQ
  • side_navigation
  • Antigravity CLI
  • >
  • Conversations

Managing conversationslink

Resume prior development threads, scope active histories to local workspaces, and fork conversations to experiment with alternate architectures.

Workspace scopinglink

To maintain context hygiene, Antigravity CLI scopes conversation histories directly to your current working directory. When you launch agy from a specific directory, the agent only displays and resume sessions associated with that specific local repository or subdirectory.

This prevents context pollution, ensuring that the agent’s semantic memory and token limits remain focused solely on the relevant codebase.

Resuming sessionslink

You can return to a prior conversation at any time to continue an implementation, refine a solution, or recover from an interrupted session.

Antigravity CLI supports both an interactive Session Picker TUI overlay and direct command-line flags (agy -c / agy --continue) to resume threads instantly based on your active workspace.

For a complete walkthrough of the interactive picker, keyboard shortcuts, and details on how the directory-scoped session cache works, see the dedicated Resume Command Guide.

Branching with /forklink

When engineering a complex feature, you may want to explore multiple design alternatives without losing your progress. The /fork command enables safe, parallel experimentation.

text
/fork

(Alias: /branch)

The /fork command clones your entire conversation history up to the current turn into a new, independent session.

Forking workflowlink

  1. Type /fork inside the prompt panel and press Enter.
  2. The CLI allocates a new unique session ID and duplicates your existing workspace state and agent thread.
  3. Your active terminal switches immediately to the new branch.
  4. If the experiment fails, run /resume to restore your original, stable conversation branch.
lightbulb
Branching Filesystems: Forking clones the conversation thread, not your local git checkout. To fully isolate files during parallel forks, use git branches or stash local changes before testing contrasting approaches.

Next stepslink

Explore how the agent handles complex, asynchronous operations and parallel tasks:

  • Background Tasks & Subagents: Monitor subagents and handle fast-path approvals.
  • Settings, Rendering & Keybindings: Configure rendering buffers and override JSON preferences.
  • Permissions & Sandbox: Manage security profiles and system command lists.
Reviewing Artifacts
Choose an execution mode
On this Page
Managing conversationsWorkspace scopingResuming sessionsBranching with /forkForking workflowNext steps