I’m using Antigravity Remote Agents (web interface) and attached a Google Drive folder as a project resource via Project Settings > Resources > Add Resource > Google Drive (using the Google Drive Picker).
Observed behavior:
The remote agent can see the attached folder itself (and even a subfolder inside it) using gdrive readonly ls <folder_id>.
However, all existing files inside the folder/subfolder are invisible — gdrive readonly ls returns an empty list for the folder contents.
Only files/items individually selected in the Picker appear in gdrive readonly ls.
Why this seems to happen: It looks like the Google Drive plugin uses the per-file drive.file OAuth scope, so selecting a folder in the Google Drive Picker only grants access to the folder object itself, not to the existing files inside it.
Expected behavior / Feature request: When attaching a Google Drive folder to a Remote Project, it would be great if the agent could automatically access the files (and subfolders) inside that folder—without having to manually select every single file in the Picker.
Thank you for the spot-on diagnosis—selecting only a folder object in the Google Drive Picker grants per-item access to that folder ID without automatically expanding authorization to pre-existing child files.
We’ve passed your feature request for recursive Drive folder access to our team. In the meantime, two quick options avoid clicking files one by one:
Batch-select inside the Drive Picker: Open the folder inside the Google Drive Picker and press Ctrl+A (Cmd+A on macOS) to select all files in that folder at once so gdrive readonly ls can read them.
Upload .zip archives (or connect GitHub) for nested trees: Attach .zip bundles under Project Settings > Resources > Uploaded files (up to 8 MiB per file and 50 files / 100 MiB per project, staged at /home/antigravity/upload), or connect a GitHub repository for larger codebases.
Let us know if either workflow unblocks your project.
Thank you for the response and for passing the feature request along to the team!
Those workarounds definitely help for getting started, and I understand Git/GitHub is a great fit for codebases. However, for non-coding tasks (such as working with documents, notes, research, or general knowledge work), setting up a GitHub repo or repeatedly re-uploading .zip snapshots is rather impractical, especially when working collaborativly.
Being able to work live inside a Google Drive folder (access subfolders and pick up new or updated files directly without manual re-selection) would make Remote Agents much more useful for everyday Drive workflows. Just like in the App.