Feature Request: Unified Environment Sync (UES) to fix Agent Desync

Google Antigravity
, , ,
1

Problem: Current “Activation Friction” causes the Agent Manager to desync from the Terminal’s .venv, leading to persistent ModuleNotFoundError during Python workflows.

Proposed Solution (Unified Environment Sync):

  • Auto-Provisioning: IDE should detect requirements.txt/uv.lock on folder-open and automate .venv creation.

  • One-Click Sync: A status bar button to lock the Agent’s interpreter path to the active Terminal session.

  • Persistent Inheritance: Force all agent sub-processes to inherit the terminal’s active environment variables.

I have identified the logic gaps in the current implementation and am looking for the right path to contribute this fix.

2

To expand on my initial proposal: I’ve drafted a logic flow for the EnvironmentResolver that could utilize the vscode.terminal.onDidWriteData listener. This would allow the Agent to dynamically inherit the PATH from the terminal’s active .venv without manual re-configuration. Has the team considered a ‘Sticky Environment’ state for the Agent Manager?