Skip to main content
The Google Drive replica implements 26 endpoints of the Drive API v3 for one signed-in account’s My Drive, with Docs, Sheets and Slides stored as text. Its key is google-drive. It was tested with @googleapis/drive.

Connect

Node
This is what ancha connect google-drive --lang ts prints. Google’s client takes the replica as a per-request rootUrl ending in /; a global rootUrl keeps only the origin and drops the path.

Endpoints

All 26 endpoints are partial. Anything else returns HTTP 501 with Google’s error shape and x-ancha-gap: 1.

Starter data

The google-drive-starter dataset is the My Drive of ancha@acme.example in the domain acme.example, with eleven users and thirty files. The agent sees what is shared with it: the company folder Acme, which everyone in the domain can edit, and a few files shared directly. ancha sandbox configuration --tools google-drive --json prints every file with its ID, owner, permissions and content.

Checks

Google Drive has no state checks. Use trace checks, for example { called: "POST /drive/v3/files/*/permissions" } or { not_called: "DELETE /drive/v3/files/*" }.

Limits

  • My Drive for one signed-in account: no shared drives, push notifications or resumable uploads.
  • Exports cover text, Markdown, HTML, CSV and TSV; PDF and Office exports are coverage gaps.
  • Sharing notifications are recorded in state, never emailed.