Run Multiple Antigravity Accounts.
Independent Sandboxes. Zero Quota Stalls.
Run multiple Google accounts side-by-side in strictly isolated sandboxes without relogging. Dual quota pools prevent workflow stalls, instant Spotlight access, 0 MB background RAM.
Independent Sandboxes. Zero Quota Interruption.
Keep multiple Google accounts open simultaneously with completely separate rate limits.
Engineered to Solve Native Limitations
Standard Single-Account Setup
- × Single Quota Ceiling: Frequent 429 quota exhaustion. Tasks halt while rate limits cooldown.
- × Disruptive Account Switching: Switching accounts forces full sign-out, aborting running agent trajectories.
- × Context & Repository Pollution: Enterprise Workspace code and personal repositories commingle in one environment.
- × Blank Slate Friction: Manually passing data dirs loses custom keybindings, MCP servers, and agent skills.
ParaGravity Architecture
- • Multi-Quota Bandwidth: Each instance connects to its own Google account with an independent quota pool.
- • Native Side-by-Side Windows: Keep corporate and personal accounts running in split screens simultaneously.
-
•
Hardware-Grade Sandbox: Official Chromium
--user-data-dirand POSIX0700permission isolation. -
•
Zero-Friction Inheritance: Pass
-ito clone settings and link MCP tools while isolating credentials.
Hand It Off to Your AI Agent
Don't want to run manual setup commands? Simply paste this directive into your AI Agent.
Please configure ParaGravity for me to enable parallel Google Antigravity multi-account execution: 1. Read the setup spec at: https://raw.githubusercontent.com/edison-land/paragravity/main/docs/agent.md 2. Install ParaGravity on my machine via the official installer: curl -fsSL https://raw.githubusercontent.com/edison-land/paragravity/main/install.sh | bash 3. Create an isolated sandbox profile named "work" inheriting my current settings and MCP tools: pgrav create work -i 4. Verify the setup with `pgrav list` and confirm when ready.
Pure Engineering. Zero Bloat.
Zero persistent daemon processes. Standard system launchers with pure Python 3 runtime.
Zero binary modification. Official Chromium sandbox flags. Native untouched Google OAuth flow.
Registered into macOS ~/Applications and Windows Start Menu for instant OS-level searchability.
Owner-only directory ACLs ensure OAuth tokens and local cache stay strictly unreadable by other users.
One-step inheritance of keybindings, editor configs, skills, and MCP tools while isolating credentials.
Built-in zero-dependency Matrix dashboard and floating widget HUD for multi-instance management.
Designed for Developer Velocity
pgrav create work -i --launch
pgrav list
pgrav launch work ~/Projects/backend-api
pgrav web
Frequently Asked Questions
Does this violate Google ToS or risk banning my accounts?
No. ParaGravity utilizes standard Chromium command-line options (--user-data-dir), the officially supported sandbox partitioning flag. No binary executables are decompiled or patched, and the native Google Cloud OAuth flow remains untouched.
Are my Google OAuth tokens and credentials secure?
Yes. All sandboxes reside locally on your disk under ~/.antigravity-profiles/ with owner-only (0700/0600) permissions. ParaGravity contains zero telemetry and makes zero outbound network requests.
Can I inherit my keybindings and MCP servers?
Yes. Pass -i (or --inherit-config) when provisioning a profile. It automatically clones editor settings and links MCP configurations without leaking credentials or conversation histories.
Is Windows supported?
Yes. ParaGravity provides cross-platform parity on macOS and Windows (PowerShell, CMD, and Git Bash MSYS2). It generates native Windows Start Menu shortcuts for Win + S indexing.
Ready to scale your agent workflow?
Deploy ParaGravity in seconds with a single terminal command.