VidbyteVidbyte

Browse docs

Google Drive connection

APIDashboard
OverviewQuickstartAPI KeysPricingSDKsCLIPlatform connectionsGitHubSlackGoogle Drive

Not available yet

Google Drive context in vidbyte-cli

No released or main vidbyte-cli reads Google Drive. The Drive sign-in and file reads this page used to describe were designed but never released; pass a downloaded file instead.

What is not available

None of the following exists in the released CLI (0.3.4) or on the CLI's main branch.

  • No Drive sign-in — No CLI reads VIDBYTE_GOOGLE_CLIENT_SECRETS or a --client-secrets file, so setting either in a shell or in PowerShell changes nothing.

  • No connections command — The planned connections login google-drive flow and its drive.readonly scope were never merged; running it ends in "No such command".

  • No file reads — No CLI command fetches a Drive file by ID or URL.

Give an agent a Drive file today

Download the file, then pass it with --files.

  1. Download the file as text

    In Google Docs, choose File > Download > Plain text (.txt). For other files, copy the part the agent needs into a .txt or .md file.

  2. Pass the file to an agent

    The Suggestion Agent reads each --files path as context; it accepts .txt, .md, and .json files, and you can repeat the option. This works in the released CLI (0.3.4).

    Context from a file

    bash
    vidbyte-cli agents suggest run --goal "Ship the billing page this week" --files context.md

Next steps

GitHub

Link a GitHub account for the bug finder; included in the released CLI (0.3.4).

Slack

Slack context reads are not available in any released CLI.

All platform connections

Return to the connection overview.

Run your first agent

Put the context you saved to work with a Vidbyte agent.