Problem
Multigravity currently works well for full profile isolation, cloning, and export/import of entire profiles.
However, there does not seem to be a supported way to move only the Antigravity AI chat history/context between profiles without also
moving account/auth-related state.
This is a real limitation when using multiple profiles for account isolation but still wanting to preserve useful AI conversations,
context, artifacts, and session history.
Current behavior
Copying the obvious AI-related directories manually, such as:
.gemini/antigravity/conversations
.gemini/antigravity/brain
.gemini/antigravity/context_state
.gemini/antigravity/knowledge
is not enough for Antigravity to recognize the transferred conversations in the UI.
In my testing, after copying conversation data into another profile:
- the Agent chat opens empty
Past conversations remains disabled
- the copied conversation files exist on disk, but the UI does not register them
At the same time, copying broader state like globalStorage / workspaceStorage appears risky because those locations may also
contain account/session-specific data.
Expected behavior
There should be a supported way to transfer or import only AI conversation/context data between profiles, without carrying over auth/
account state.
Examples of useful workflows:
- transfer one conversation from profile A to profile B
- import all conversations from one profile into another
- export/import AI chat history only, separately from the full profile
- restore AI context on another machine without restoring login/session state
Suggested feature
One of these would solve the problem:
Option 1: chat-only export/import
Commands like:
multigravity export-chats <profile> [output]
multigravity import-chats <archive> <profile>
### Option 2: direct profile-to-profile transfer
multigravity transfer-chats <source-profile> <target-profile>
### Option 3: reindex imported AI data
A command like:
multigravity reindex-chats <profile>
so that if a user copies supported AI data folders manually, Multigravity can rebuild whatever index/state Antigravity needs for
those chats to appear in the UI.
## Requirements
Ideally this feature should:
- transfer chat history and context only
- preserve conversation attachments/artifacts where possible
- avoid copying auth/account/session tokens
- make imported conversations appear in the Antigravity UI
- avoid corrupting the destination profile
- handle duplicate conversation IDs safely
## Why this matters
Multigravity’s main value is profile isolation. But right now, that same isolation makes useful AI history effectively trapped inside
each profile unless the user moves the whole profile.
A first-class chat/context migration feature would make profile-based workflows much more practical.
## Environment
- OS: Linux
- Antigravity version: 1.107.0
- Multigravity Pro
Thanks, this would be a very useful addition.
Problem
Multigravity currently works well for full profile isolation, cloning, and export/import of entire profiles.
However, there does not seem to be a supported way to move only the Antigravity AI chat history/context between profiles without also
moving account/auth-related state.
This is a real limitation when using multiple profiles for account isolation but still wanting to preserve useful AI conversations,
context, artifacts, and session history.
Current behavior
Copying the obvious AI-related directories manually, such as:
.gemini/antigravity/conversations.gemini/antigravity/brain.gemini/antigravity/context_state.gemini/antigravity/knowledgeis not enough for Antigravity to recognize the transferred conversations in the UI.
In my testing, after copying conversation data into another profile:
Past conversationsremains disabledAt the same time, copying broader state like
globalStorage/workspaceStorageappears risky because those locations may alsocontain account/session-specific data.
Expected behavior
There should be a supported way to transfer or import only AI conversation/context data between profiles, without carrying over auth/
account state.
Examples of useful workflows:
Suggested feature
One of these would solve the problem:
Option 1: chat-only export/import
Commands like: