corresync

Your project, your consent

Connect Google without waiting for Corresync’s OAuth review.

Create a Desktop OAuth client in a Google Cloud project you control. Corresync validates the downloaded file, stores its generated credential in your OS keyring, and leaves sign-in to Google in your normal browser.

Start the illustrated setupCompare providers
User-owned OAuth is available; Corresync-managed OAuth is dormant.

The adapters have synthetic contract coverage and remain live-unobserved. Your Google project, audience, quota, warnings, and organization policy still apply.

Four browser screens

Set up the smallest Google project that fits.

These are annotated maps, not screenshots of an account. Google may rename a menu; the destination and security boundary stay the same.

01 · Project

Create or select a project you own

Open Google Cloud Console and use the project picker. Do not borrow another application’s client or secrets.

console.cloud.google.com
Select a project
My Corresync · project you control
NEW PROJECT
The project owns the consent identity and quota.

02 · APIs

Enable only what you selected

Enable Gmail API for mail, Google Calendar API for Calendar and Meet event links, and Google Tasks API only for Tasks.

APIs & Services / Library
API Library
Gmail API · Calendar API
Tasks API · only if selected
No Chat, Drive, Contacts, or admin API is needed.

03 · Audience

Choose the honest audience and scopes

Use Internal only for an eligible single Workspace organization; otherwise External. In Testing, add your account as a test user. Testing authorizations expire after seven days.

Google Auth Platform / Audience
Audience
External · personal and other accounts
Internal · eligible organization only
Data Access: Gmail modify; Calendar list read + events; one Tasks scope.

04 · Client

Create a Desktop app and download JSON

Under Clients, choose Desktop app—not Web application, service account, or API key. Download the JSON and keep it private.

Google Auth Platform / Clients
Create OAuth client
Application type · Desktop app
DOWNLOAD JSON
Corresync uses 127.0.0.1 with a fresh random local port.

Secure local handoff

Let guided setup do the careful part.

Run corr setup, select Google and the services you want, then choose “Import downloaded client JSON”. Review the client ID, loopback URI, scopes, and separate keyring handles. Account setup does not sign in. 

$ corr setup
$ corr auth login --account personal
$ corr doctor --account personal

For scripts, use corr auth google-client import FILE --key HANDLE first. Never paste the generated credential into TOML, a shell argument, MCP, an issue, or support output. Corresync deliberately does not delete your downloaded file.

Before you publish

Personal use may not require verification—but limits still matter.

Google currently lists personal use under 100 users and qualifying internal use among cases where verification is not mandatory. Unverified warnings, user caps, restricted-scope policy, organization controls, and Google’s current terms still apply. Check Google’s official rules before changing from Testing to production.

Ready when you are

Create the client, then keep everything local.

Google sign-in remains in Google’s browser; mail, calendar, tasks, and credentials do not pass through a Corresync server.

Install CorresyncOpen the technical guide