Problem / Motivation
A lot of working files live in Google Drive, and nanobot can't see them. Right now you download the file yourself and put it in the workspace before the agent can read it.
Proposed Solution
A google_drive tool that authenticates with a service account. You share a folder with the account's email, paste the key and the folder ID into Settings > Apps, and the agent can list, search, read metadata for and download files under that folder. Nothing outside the listed folders is reachable.
It's read-only (drive.readonly), so it can't change anything in Drive. Google Docs, Sheets and Slides are exported as text, CSV and PDF. Downloads go to a subfolder of the workspace and are capped at 50 MB by default.
The key is stored in the config directory with owner-only permissions. Saving the settings turns the tool on in the running gateway; a restart is only needed if the Google libraries were installed in the same step. The libraries come from a new drive extra.
Alternatives Considered
OAuth with a user account would reach everything the user can see, but it needs a consent screen and token refresh, and it's too much access for a bot that only needs a few folders. A Drive MCP server would also work. The tool keeps the folder allowlist and the download path under the existing workspace rules, which is why I'd rather have it in nanobot.
Related Component
Other (agent tool and WebUI settings).
I have a working draft and will open a draft PR for it.
Activity
0No activity yet.