Repository navigation
Instances
Ra1nify edited this page Oct 31, 2026
·
1 revision
An instance is one Antigravity run slot. Each instance owns a separate UserData, .gemini, and AppData. Processes and sign-in state are not shared.
| Column | Meaning |
|---|---|
| Name | Set at creation, renameable |
| Short ID | First 8 characters of the instance ID |
| Account | Bound account. Shows Unbound when none |
| Projects | Number of bound projects |
| Status | Running / Stopped |
| PID | Process ID while running |
| Button | Behavior |
|---|---|
New instance |
Opens the creation dialog; name, account, and projects |
Refresh |
Re-reads process state and ports |
Stop all |
Terminates every running instance process |
| Button | Behavior | Precondition |
|---|---|---|
Launch |
Starts Antigravity with this instance sandbox | Core installed |
Stop |
Terminates the instance process | Instance running |
Configure |
Opens instance settings: name, account, projects, proxy | — |
Delete |
Removes the definition and the sandbox directory | Instance stopped |
- Verify the core directory exists;
- Check the account mutex. If another running instance holds the account, show a risk confirmation;
- Create the instance
UserDataand.geminidirectories; - Mount the shared pool:
skills,plugins,mcpas junctions to<install>\shared\; - Mount project memory: whole-directory junction for a single bound project; per-conversation junctions for multiple;
- Inject material and localization code into
utils.js; - Start
Antigravity.exewith a dedicated--user-data-dir.
One account is usable by one running instance at a time.
| State | Handling |
|---|---|
| Account free | Launch |
| Held by the same instance | Launch |
| Held by another instance | Show risk confirmation. Confirming terminates the prior process, clears the lock, and launches |
| Held but the process is gone | Treated as a stale lock; can be cleared |
Stale locks are cleared with Force unlock on the Accounts page.
| Bound projects | Mount | Sharing |
|---|---|---|
| 0 | Instance-owned empty directories | None |
| 1 | Whole-directory junctions for brain and conversations
|
Two-way. New conversations are written into the project |
| ≥2 | Instance-owned directories plus per-conversation junctions | One-way snapshot. Existing project conversations are mounted; new instance conversations are written back when the process exits |
In multi-project mode, write-back requires both:
- the instance process exits;
- the conversation
workspace_uriscontains the path of a bound project.
Otherwise the conversation stays in the instance sandbox and is invisible to other instances.
- Terminate the process;
- In multi-project mode, write back conversations;
- Release the account mutex;
- Update instance state and the running flags in
projects.json.
Deleting an instance removes:
-
data\instances\{id}\(sandbox,.gemini,UserData) - the instance entry in
data\instances.json
Project memory stores and the shared pool are not touched. The delete button is unavailable while the instance runs.
| File | Role |
|---|---|
data/instances.json |
Definitions and bindings |
data/instances/{id}/ |
Sandbox |
src/Gravityless.Core/Services/InstanceService.cs |
Create, launch, stop, mount |
src/Gravityless.App/Resources/Languages/*.xaml |
Text keys Instances_*
|
Gravityless · GPL-3.0 · English | 简体中文