Context from your tools
Connect platforms the CLI can read
Named OAuth connections let vidbyte-cli read selected resources from GitHub, Slack, and Google Drive. The CLI verifies each account and keeps its OAuth tokens in the operating system keyring.
Choose a platform connection
Each connection has its own sign-in flow and supported reads. Start with the service you want to use; its page walks through client setup, sign-in, verification, and example reads.
Connect a platform for context reads
Use connections login to authorize a GitHub account, Slack workspace, or Google Drive account. Every platform uses the same commands: the CLI opens the provider's sign-in flow, verifies the account, and stores OAuth tokens in the operating system keyring.
Authorize a platform
Pick the platform you want the CLI to read from. Each one opens its own sign-in flow in your browser, and the CLI saves the token only after it verifies your account or workspace.
Starts the GitHub device authorization flow.
GitHub connection
bashvidbyte-cli connections login githubStarts the Slack PKCE authorization flow.
Slack connection
bashvidbyte-cli connections login slackStarts installed-app authorization for Google Drive.
Google Drive connection
bashvidbyte-cli connections login google-driveList saved accounts
Shows the connection names in the current profile without contacting providers.
Connection list
bashvidbyte-cli connections listVerify one account
connections statusrechecks the account behind the selected connection name and refreshes its tokens when needed.Connection status
bashvidbyte-cli connections status githubRemove it when you are done
Logs out by connection name and removes the saved account.
Remove a connection
bashvidbyte-cli connections logout github
connections read fetches only supported resources, such as a repository, a pull request, a Slack channel's recent history, or a selected Drive file. These connections do not replace the OpenAI key used by local runtimes or the Vidbyte API key used for your account.
Connect more than one account on a platform
--name gives a connection its own name. Use that name in status, read --connection, and logout to pick the account.
Name a connection
vidbyte-cli connections login github --name work-githubScoped to a profile — Connections belong to the selected CLI profile and can have custom names.
Tokens stay in the keyring — OAuth token envelopes stay in the OS keyring; non-secret account metadata is stored separately. The CLI does not use the restricted-file fallback for OAuth tokens.
Model API keys use a different command
vidbyte-cli provider login <model-provider> is for model API keys such as OpenAI. It verifies a key and stores it for local runtime execution; it does not connect a GitHub, Slack, or Google account.
Model API key —
vidbyte-cli provider login openaistores a model key for supported local runtimes.Platform account —
vidbyte-cli connections login githubconnects an account the CLI reads context from.