Google Integrations (Calendar, Drive, Sheets)
Calendar, Drive and Sheets behind one shared Connect Google consent — and all three are agent-facing inside their own panels' AI chat, so you ask in plain English and Claude calls the right tool. What the Calendar panel shows and how syncing and notifications behave.
On this page
What it is
Omniscio connects to Google Calendar, Google Drive, and Google Sheets through a single shared OAuth (one "Connect Google" click gives all three). These integrations are agent-facing inside their own panels: Claude gets them as tool-use calls inside a conversation loop in the Calendar panel's ask bar and the Drive and Sheets panels' AI chat, so you ask in plain English ("what's on my calendar Thursday", "create a sheet with those numbers", "create a Drive folder called 2026-campaigns and share it with sarah@...") and the agent decides which tool to call, Omniscio executes it via the googleapis library, and the agent continues its response using the result. A plain Claude session — one you start in the sidebar — has none of these tools unless you attach the Google Workspace MCP to it yourself (see the last paragraph of "How it works"). Agent responses come back as markdown with linked Drive files, formatted Sheets tables, or concise event summaries. Calendar additionally has a real browsing UI inside Omniscio: the Calendar sidebar project opens a full panel with Agenda / Week / Month views, an event editor, an AI chat drawer, and a Today/Tomorrow sidebar list (see "The Calendar panel" below).
Where to find it
How to use it
- Connect Google once — from the one Google Account card. Both Settings → Google Workspace and Settings → Email & Summaries show a single Google Account card at the top with one Connect (and, once connected, Disconnect) button. Gmail, Calendar, Drive, and Sheets all share this one sign-in, so each product just shows a derived "Ready" line underneath instead of its own separate Authenticate button. Your normal web browser opens at Google's sign-in (any passkey works there); approve the scopes in one go. Omniscio catches the redirect on a loopback HTTP server, encrypts the refresh token, and stores it. Because every Google surface reads one shared connection store, connecting (or disconnecting) anywhere updates all of them live — no stale "still disconnected" panels. Disconnecting revokes the token at Google, clears everything at once, and deletes the local data Omniscio built from Google — the mailbox copy, the Google Meet list, the email samples saved from Gmail, and the people and profile details built from your email (past daily digests and writing-style guides you created are kept). Connecting a different Google account does the same cleanup on the account you are leaving — its mailbox copy, summaries, learned signals and cached data are removed (and its grant revoked) before the new account is recorded, so one person's mail never shows up under another's sign-in. (Invariants: google-account-connection-contract.md.)
- Enable the integrations you want. Each integration has its own enable flag (
gmailEnabled,calendarEnabled,driveEnabled, etc.) so you can turn on, say, Calendar without using Drive. The one consent covers every integration — but a switched-off integration is left alone: the daily digest reads Gmail only whilegmailEnabledis on and Calendar only whilecalendarEnabledis on (and a new install leaves both out of the digest until you add them), and the Gmail bug-intake reader makes no Gmail call until a project has bug intake set up. - Ask the agent something — in the panel, not a plain session. Use the Calendar panel's ask bar, or the Drive / Sheets panel's AI chat: "check if I'm free Thursday at 3pm", "create a Drive folder called 2026-campaigns and put the assets from #design-review inside", "read the first sheet of Q1 budget and tell me total spend". The agent decides which tool to call from the 23 available (Calendar 6, Drive 7, Sheets 10), executes it through the token-loop, and responds. These tools live behind the panels' own chat drawers (
CALENDAR_AI_CHAT/DRIVE_AI_CHAT/SHEETS_AI_CHAT); a Claude session started from the sidebar does not have them. - Read the results. Drive operations come back with
webViewLinks that are clickable. Sheets operations render as markdown tables. Calendar operations return event summaries with links to open the event in Google Calendar's web UI. - Separately: Drive via MCP — force-disabled. This read-only Drive MCP (search/list/read/info/quota over the user's EXISTING Drive) needed the restricted
drive.readonlyscope, so it is now force-disabled and the shared OAuth requests onlydrive.file— see the scope-change note in drive-integration.md. The built-in Drive tools (step 3) degrade to create-only; full Drive over existing files is moving to a bring-your-owngogCLI path (follow-up). - Google Doc paste-to-import (off by default). Settings → Google → Drive → toggle Auto-import pasted Google Doc URLs on. With it on, pasting a
https://docs.google.com/document/d/...or/presentation/d/...URL into the chat composer fetches the doc as markdown (or slides as a PDF) and inserts it; without it on, the URL pastes as plain text. Hold Shift while pasting to force plain-text paste even when the toggle is on. The integration uses the same Google OAuth as Drive — if you haven't connected Google yet, a "Connect Google to import this doc" toast appears with a button that launches the unified consent flow. If Drive cannot see the Doc (the connection holds onlydrive.file, so it answers "not found" for a Doc the app never created), the import retries through the Google Docs API before showing you anything — so a Doc you own but never opened with Omniscio still comes in, every tab included.- Inline images are stripped from the imported markdown. Google's
text/markdownexport inlines every embedded image as a base64data:URI — typically a 50–200 KB payload apiece, usually clustered at the bottom of the document as reference-style definitions ([image1]: <data:image/png;base64,…>). A single image-bearing Doc can balloon a 2k-token document to ~200k tokens once pasted, so Omniscio removes thosedata:image references (both reference definitions and inlineforms) and keeps the document's text and structure. Normal links and external image URLs (https://…) survive untouched. This mirrors the equivalent strip on the clipboard HTML-paste path — see paste-rich-text.md. It applies only to the Docs-as-markdown path; Slides imported as PDF keep their visuals natively.
- Inline images are stripped from the imported markdown. Google's
- Sheets URLs paste as text. Pasting a
https://docs.google.com/spreadsheets/d/...URL drops the URL into the textarea unchanged — there is no paste-time fetch for Sheets, so the toggle in step 6 doesn't apply. The first time you paste a Sheets URL, a one-time dismissible hint suggests asking Claude to read or edit the sheet directly in chat (which uses the 10 Sheets tool-use calls described in step 3). Click "Don't show again" to silence it. - Import a Google Doc as markdown over the CLI (off by default). The same import capability is exposed to external agents / scripts / the phone over Omniscio's local control server as
POST /gdoc/import(127.0.0.1:19519) — the exact reverse ofPOST /gdoc/publish(markdown → Doc). Send{ "url": "<a Google Doc URL or a bare doc id>" }with the bearer token; get back{ ok: true, data: { title, markdown, url } }(full markdown inline). Bearer-auth, 10/min cap, gated by the samegoogleDocImportEnabledtoggle as step 6 (403FORBIDDEN—Google Doc import is off. Turn it on in Settings → Connections → Google Workspace.— when off). Docs only — a Slides/Sheets link returnsVALIDATION_FAILED; every other failure now carries the SHARED error vocabulary instead of the old ad-hocGDOC_IMPORT_*family (each domain code is mapped onto it insrc/main/services/cli/cli-server-gdoc-routes.ts):FORBIDDENfor not-connected / no-access / expired-token / drive-not-authorized / drive-scope-limited,NOT_FOUNDfor a missing doc,RATE_LIMITED, andSERVICE_UNAVAILABLEfor a timeout or a network failure — each with a plain message that never leaks the connected email or raw Google errors. Because the connection holds onlydrive.file, Drive answers "not found" for a Doc it did not create — so a Doc whose Drive read is refused is retried through the Google Docs API, which the same connection is already authorized for (auth/documents), and the Doc imports in full (every tab). Only when both roads refuse does the link come backdrive-scope-limited(FORBIDDEN, neverNOT_FOUND), with a message about the connected account rather than a claim that the link is wrong. Sheets and Slides have no second road yet (a pre-existing Sheet is T-580; a Slides link needs a scope the app does not request), so for those the same code says something different and true — that Omniscio can read only the files it created, with saving-and-importing as the way through. It reuses the same converter as paste-import, so the markdown (with base64 images stripped per step 6) is identical whichever way you import. Full route reference: cli-server-gating.md § /gdoc/import.
The Calendar panel
Beyond the agent tools, the Calendar virtual project in the sidebar opens a real calendar UI (src/renderer/src/features/calendar/):
- Three views: Agenda (the default), Week, and Month, switched by tabs in the panel header (
CalendarHeader.tsx, view state incalendar-store.ts). The panel loads the next 90 days of events and the header carries an event count plus New Event and Refresh buttons. - Times are in your own time zone: every event shows at your computer's clock, the way Google Calendar shows it, even when a colleague created it in another zone (a meeting booked for 11:00 AM New York time reads 10:00 AM in Chicago). Editing such an event shows your clock too, and saving keeps the event's original zone so a repeating series still follows it. Rule:
.claude/memory/contracts/calendar-timezone-display-contract.md. - Every subscribed calendar, with show/hide: the panel, the sidebar Today/Tomorrow list, and the daily digest show events from ALL your Google calendars at once, each colored by its calendar (not just the primary one). Settings → Calendar → "Calendars to show" lists every calendar with a checkbox — uncheck the noisy ones (holidays, birthdays, shared team calendars) to hide them (hiding a calendar also stops its "starting soon" reminders — the reminder scan runs over the same visible set); a calendar you subscribe to later appears automatically. The same checklist also opens from the gear at the right edge of the Calendar panel's tab row — the panel's own settings, a small "Calendar settings" panel holding the "Calendars" list (
CalendarPanelTabs.tsx+CalendarVisibilityList.tsx), so you can toggle a calendar without opening Settings. The gear sits in the tab row rather than inside the list, so hiding every calendar can never leave you with no way back. While Mission Control is on, the same panel also holds a Mission Control due dates block under the list — a show/hide switch for project due dates and a per-project checklist (see pm-calendar-overlay.md). Both surfaces write the same setting via the sharednextHiddenIdshelper. Stored ascalendarHiddenIds(the unchecked set; default empty = all shown). Backend:resolveVisibleCalendarIds()incalendar-api-service.tsreads across the visible set and tags each event with itscalendarId. - Event popover (
EventPopover.tsx): click any event for its details with Edit and Delete actions; Delete goes through a confirm dialog. - Event editor (
EventForm.tsx): title, all-day switch, start/end, location, description, attendees as validated email chips, a recurrence builder (RecurrenceBuilder.tsx: daily / weekly / monthly / yearly presets or a custom rule with interval, weekdays, and end date), reminders (keep Google calendar defaults or add custom notification/email overrides from 5 minutes to 2 days before), and a target-calendar picker. Used for both create and edit. - A written event needs a usable start and a usable end:
createEventrequires both edges andupdateEventjudges only the edges the patch sends, so an all-day event (twodates), a timed event (twodateTimes, offset or offsetless with atimeZone) and a partial reschedule all work, while a time field carrying no date — Google's400 Missing end time.— is refused inside the app with a plain sentence instead of being sent. The check is deliberately looser than Google's own grammar, because refusing a value Google would have accepted is the worse failure. Two related classifications ride on it: a 400 from Google for the event body is a caller condition (logged as a warning and answered as a bad request, never a crash report), while a dead Google sign-in — which also arrives as a 400 (invalid_grant) — is left alone so it keeps its existing "reconnect Google" handling. Permission refusals, rate limits and outages are likewise untouched. On the CLI,POST /google/calendar/eventsstates the same rule in its schema and answers400 VALIDATION_FAILED, and a batch whose items are all refused answers 400 rather than 502. - Drag in Week view (
useDragEvent.ts): drag an event body to move it to a new time, or drag its bottom edge to resize; both persist through the store'supdateEvent. - AI chat drawer (
CalendarChatDrawer.tsx): a persistent ask bar at the bottom of the panel ("Ask about your calendar..."); expands into a 280px thread (Esc collapses). The bar is the app's chat bar — the sameMessageBarComposerthe session composer renders — so it auto-grows as you type, supports text undo/redo and markdown paste, and sends on your configured Enter / Ctrl+Enter chord (Shift+Enter is a newline). When FlowVoice is enabled its dictation mic rides in the bar's left strip. Answers run through the 6 calendar tools, and each write renders a labeled badge on the reply (Created / Updated / Deleted). Requires an API-key account; theno_api_keyerror is surfaced in plain language. - Sidebar Today/Tomorrow list (
CalendarSidebarContent.tsx, the Calendar tab ofCalendarPanelTabsmounted bySessionsSidebarwhile the Calendar project is selected): today's and tomorrow's events with time, title, and location (URL locations are clickable); the current event, or one starting within 2 hours, is highlighted, and past events are dimmed. - Sessions tab (
CalendarPanelTabs.tsx,calendar-session-host.ts): the Calendar panel is a Calendar | Sessions toggle — the "Sessions" tab is the standard agent-session list ("+ New session", pause, archive, right-click menu, running-count badge), exactly like Tasks or Mind Map. A session started there is briefed as a calendar assistant and can view + manage your Google Calendar over the control server's/google/calendar/eventsroutes (GET/POST/PATCH/DELETE); it runs in a managedcalendar-agentworkspace. Every/google/calendarroute checks the Google sign-in first: signed out, it answers403with the shared not-connected body (code: FORBIDDEN) instead of a500, and the list routes never return a made-up empty calendar. See.claude/memory/contracts/session-host-contract.mdand thegoogle-apisomniscio-control surface. - Reconnect recovery: an expired/revoked Google token during a Quick Launch calendar create renders a friendly error pane with an inline Reconnect Google button that reruns the unified OAuth flow and automatically retries the same create. That heal-in-place behavior is
create-errors-are-humanized-and-heal-in-placein.claude/memory/contracts/calendar-quick-add-invariants-contract.md.
How it behaves
What the Google Account card shows
The one Google Account card at the top of Settings → Google Workspace tells you which of four states you are in, and never claims you are signed out while a Google credential still exists on the computer:
- Connected as you@example.com — the sign-in works. Reconnect and Disconnect are both offered.
- Connected here, but it could not be verified — a Google credential exists but Google would not confirm it (an expired or revoked grant, a failed check). You get Reconnect to restore access and Disconnect to remove it.
- Couldn't check your Google connection — the status check itself failed. Refresh tries again, and Disconnect stays available.
- Not connected — no Google credential is stored. Connect signs you in.
Why it matters: while a Google credential is present, DeepSeek sessions are turned off so your Gmail, Calendar and Drive data never reach it. Disconnect is therefore always offered whenever that credential exists — including when the check failed — so that instruction is never a dead end. One Disconnect clears every source, including a Google connection made through Composio.
Signed in with the gog CLI only
If you signed in to Google once through the gog command-line tool and never connected Google inside the app, Omni and Mission Control still read your Google data through gog, so you never sign in twice. Key facts:
- What works: the Gmail status, inbox search, opening a thread, recent senders and the label list (
GET /gmail/labels) on the command-line routes, the Google Calendar list and event reads, the Google Drive status and file list (GET /drive/status,GET /drive/files), and the What Next email, calendar, Google Docs and Meet sources. - Reads only. Sending, labeling, archiving, every calendar change and every Drive change still need the in-app Google sign-in, and gog itself is told to refuse writes. Reading a Drive file's contents, downloading it and the Drive storage quota also still need the in-app sign-in.
- The status says which sign-in answered:
GET /gmail/statusandGET /drive/statuscarryvia: "gog"orvia: "app". - When gog cannot help, the reason is named. A locked gog keyring, a wrong saved keyring password, or a gog sign-in that has expired, shows that cause and its one-time fix instead of a plain "not connected".
- The app can open gog's locked file keyring itself. gog's file keyring needs a password. Save it once in Omniscio as the
gogKeyringPasswordsetting: an agent offers it throughPOST /input-request(targetgogKeyringPassword) and you press Save. With direct save switched on, it saves with no click.- The password is checked before it is stored: a read-only
gog auth listmust open the keyring, or nothing is saved and the prompt says why. - It is stored encrypted, never shown in Settings or a CLI settings read, and handed only to the gog programs the app starts.
- A password already in the app's own environment (a user-level
GOG_KEYRING_PASSWORD) still wins. - Within a minute,
GET /gmail/statusanswersauthenticated: true, via: "gog".
- The password is checked before it is stored: a read-only
- The in-app sign-in always wins when it is present; background pollers, the Gmail panel and the Drive panel keep using it.
- A Drive list through gog is newest first. gog sorts by one key only, so folders are not grouped at the top the way the in-app list groups them; shared drives are left out, as they are in the in-app list.
- Rules: google-cli-fallback-contract.md (I7).
Background sync & notifications
Beyond on-demand reads, a background service (calendar-sync-service.ts) keeps your calendar fresh and drives notifications — while the Calendar integration is on, you're signed in, and you're online. It does two things:
- Change detection (~every 5 min) uses Google's incremental
syncToken(its purpose-built "what changed" cursor) per visible calendar. When something changes it (a) fires a notice, and (b) pushesCALENDAR_CHANGEDso any open calendar view reloads. A first sync is a silent baseline (no notices — every event would otherwise look new); an expired token (HTTP 410) is dropped and re-baselined.- Two kinds of notice, two separate switches. A brand-new event gets "Event added: …"; an edit to an existing one gets "Calendar updated: …". These are different news — the first is a confirmation you stop wanting once you trust the feature, the second is something you probably still want to hear about — so each is its own alert type with its own switch (Settings → Notifications → Alert types → Calendar event added / Calendar event changed). They used to be one type, which meant turning off the routine confirmations also silenced every real change. Google's incremental sync hands both over identically, so the two are told apart by comparing the event's creation and last-modified stamps (within ~2s of each other = newly added); when that cannot be determined the notice falls back to "Calendar updated", never to "added", so a real change someone else made is never routed into the switch you turned off for your own confirmations.
- Reminders (~every 1 min) fire a "starting soon" notice for each upcoming timed event crossing your lead time (default 15 min, configurable 0–120), at most once per occurrence (a small fire-once ledger survives restarts). All-day events are skipped.
Delivery is your choice — Settings → Notifications → Google Calendar reminders: a dismissible inbox alert (default), a transient toast pop-up, or both. "Added/changed" notices have their own sub-toggle (they can get chatty on a shared calendar). Settings: calendarSyncEnabled, calendarNotificationsEnabled, calendarNotificationDelivery, calendarReminderMinutes, calendarChangeNotificationsEnabled.
Every "starting soon" card manages itself — you never have to go hunting in Settings to stop them. The card carries Turn off these reminders, which flips calendarNotificationsEnabled off, toasts where to turn it back on, and archives the row — reminders ONLY, so calendar sync, the daily agenda card and the calendar views keep working, and the added / changed notices keep their own separate switches. Since every off switch now confirms first, the card tells you all of that BEFORE it acts rather than in a toast afterwards. Its primary button, Open reminder settings, deep-links straight to the Google Calendar reminders card in Settings → Notifications and flashes it, rather than dropping you at the top of the section.
This is deliberately NOT a local calendar cache — reads stay live against Google. Only two tiny operational tables back it (a per-calendar sync-token cursor + the fire-once ledger). Full invariants + the design rationale (why a cache was rejected): calendar-sync-contract.md.
Daily Agenda Card
Each morning the background service posts a "Today's Agenda" inbox card listing every event for the current day. Key facts:
- On by default for new installs (
calendarDailyAgendaEnabled: true); only fires whencalendarEnabledis also on. - Posts once per local day — idempotent on its date-stamped
dedupKey daily-agenda-<YYYY-MM-DD>: if today's card already exists (active OR already dismissed) it is NOT re-posted, so a restart never re-posts and an archived card is never resurrected. No fire-once ledger and no DB migration. - Shows up as soon as it posts — the Overseer's batch-window hold never delays it, the same as the calendar reminders (calendar-sync-contract
the-daily-agenda-is-never-held). If Omniscio was closed at the scheduled time, it posts on the first check after the app starts. - Scheduled time is
calendarDailyAgendaHour:calendarDailyAgendaMinute(default 7:00 AM local time). Configurable at Settings → Calendar → Daily agenda card (toggle) + Agenda delivery time (quarter-hour time picker). - Each event's title opens the event INSIDE Omniscio, and a small Google link beside it opens its Google Calendar page (
htmlLink) in the browser:- **7:00 AM–8:00 AM** — [Title](omniscio://calendar/event/<id>?calendar=<calendarId>) · [Google](htmlLink). The in-app link switches to the Calendar panel and pops up that event's details (see "Opening one event from a link" below). An event with no id links its title to Google alone; an event with neither link is plain text. - The links survive the inbox secret scrubber. A Google Calendar event id is long enough to look like a secret, so before 2026-10-09 every agenda and "starting soon" link was saved as
eid=[redacted]and opened a dead page. The alert chokepoint now spares Google Calendar event links (inbox-alert-contracta-recovery-pointer-is-not-a-secret); cards delivered before the fix keep their broken links. - An empty day posts a friendly "nothing scheduled today" card — no card is ever suppressed for a free day. A calendar-read failure skips the card (never posts false-empty) and logs at
warn. - Inbox-only delivery — not routed through
calendarNotificationDelivery.
Opening one event from a link
The agenda card and the "starting soon" reminder card link each event to omniscio://calendar/event/<eventId>?calendar=<calendarId> (built by calendarEventDeepLink in src/main/services/deep-link.ts). Clicking it activates the Calendar panel and selects the event, so its details popover opens. Key facts:
- Events outside the loaded days still open. The panel loads the next 90 days; anything else (an old card, a past event) is fetched by id through
CALENDAR_GET_EVENT, which now takes the optionalcalendarIdso an event on a shared calendar is found. The store action isopenEventByIdincalendar-store.ts. - A dead link says so. A deleted, cancelled or unreachable event shows "That calendar event no longer exists or couldn't be loaded." and selects nothing; with Calendar switched off the link reports that instead of landing on an empty panel.
- Navigate-only. It only shows the event, so it is never approval-gated, and it works from a closed app through the usual cold-start link path.
- "Starting soon" cards are text cards: the "In 15 min · place" line, then
[Open in Omniscio](…) · [Open in Google](…). Their Turn off these reminders button is unchanged. The added / changed notices keep their single Google link. - Rules:
.claude/memory/contracts/calendar-event-deep-link-contract.md.
Clickable events in the sidebar
When the Calendar channel adapter surfaces events in the unified inbox/search (ChannelProjectView.tsx), each event message shows an "Open in Google Calendar" link below its body (the ExternalLink lucide icon in accent colour) when the event's htmlLink begins with https://. The link opens in the system browser via openExternalUrl. The field that carries the URL is UnifiedMessage.externalUrl, set in mapEventToMessage (calendar-adapter.ts); other channel adapters leave it undefined.
How it works
OAuth lives in google-auth-service.ts: single flow, loopback HTTP redirect, encrypted refresh token stored via safeStorage. The scopes come from getOAuthScopes(): gmail.modify, gmail.settings.basic, calendar.events + calendar.calendarlist.readonly + calendar.freebusy (the narrow Calendar trio — never the full calendar scope), drive.file, spreadsheets, documents, contacts.readonly, plus meetings.space.readonly only while the in-development Google Meet feature is switched on (Google's OAuth verification approves only scopes a released feature uses; locked by tests/unit/services/google/google-auth-scopes.test.ts). The restricted drive.metadata.readonly scope that trusted-folder checks need is asked for only while the in-development Lab feature Trusted Sheets folder checks is on (isDriveFolderScopeEnabled(), drive-folder-scope-gate.ts), so a default install never requests it. gmail.modify and gmail.settings.basic are Google restricted scopes, so the app owes Google's restricted-scope verification plus an annual CASA security assessment; oauth-scopes-casa-tier2.test.ts scans all of src/ and allows no other restricted scope. Each integration has a dedicated AI service with its own tool definitions exposed to Claude's API and a token-loop that runs: agent message → Claude returns tool_use → Omniscio executes via googleapis → results appended → repeat until stop_reason='end_turn'. The three services: calendar-ai-service.ts (6 tools: list, get, create, update, delete, check_availability), drive-ai-service.ts (7 tools: list, get, create_folder, delete, move, share, quota), and sheets-ai-service.ts (10 tools: list, get, read_range, update_cells, create, add_sheet, delete_sheet, insert_rows, insert_cols, format). Each has a circuit breaker to prevent thundering-herd API storms, per-account cost tracking, and re-routes errors back as tool results so Claude can recover instead of crashing the turn. IPC surface: CALENDAR_AI_CHAT, DRIVE_AI_CHAT, SHEETS_AI_CHAT — wired by calendar-handlers.ts, drive-handlers.ts, sheets-handlers.ts (also exposing non-AI list/CRUD IPC). The read-only Drive MCP is force-disabled (it needed the restricted drive.readonly scope); mcp-registry.ts now only removes its old ~/.claude.json entry. The bundled Google Workspace MCP is off by default: it attaches per project or per session through the MCP selector (googleWorkspaceMcpEnabled, default false), and only once switched on is it composed into that session's .mcp.json, with NO secret in its env — it fetches a short-lived access token from /mcp/credential at call time. Switching it on is how a plain Claude session gets Google tools at all; the 23 panel tools above do not depend on it. Integration-enable flags live in types.ts under AppSettings.
Connecting Google through Composio (the second road)
When a direct Google sign-in is not possible, Google can be connected through the user's own Composio account instead (composio.md) — as ONE sign-in covering all five Google apps, or one per app, at the user's choice. getAuthClient() then hands out a Composio-backed client (composio-google-client.ts) whose request() forwards each googleapis call through Composio Proxy Execute, so every screen above works unchanged. isGoogleConnected() covers both roads, a direct sign-in always wins, and Google background checks run at most every 15 minutes on the Composio road (google-poll-floor.ts). Features that need a raw Google token (the Workspace and Drive MCP servers, plugin sign-in, Meet) refuse plainly there.
Until Google approves Omniscio's own sign-in, Connect Google takes the Composio road automatically. Every connect button ends in IPC GMAIL_AUTH, which calls connectGoogle(): a person with a direct sign-in (or, once approved, anyone) gets the official loopback sign-in; otherwise a saved Composio key opens the Composio Google sign-in and waits up to 5 minutes for a new active connection, and no key opens the Composio tab with a plain "add your Composio key" message. GMAIL_STATUS reports connectRoad (official | composio) so the Gmail gate's main button connects through Composio directly and its second button becomes Sign in with Google directly (sends road: 'direct'). A failed connect now shows its message as a toast instead of silently doing nothing. Plugin Google sign-in and the Supermail grant still use the official road, because they need a raw token Composio never hands out. Details: composio.md.
Related
- gmail-integration.md — shares the same OAuth + token storage
- composio.md — the second way to connect Google, through the user's own Composio account
- mempalace-memory.md — another example of Omniscio registering an MCP server for the CLI
- cloud-storage.md — the other file-storage integrations: Dropbox and Microsoft OneDrive as connected sidebar panels.
Last verified 2026-11-04