You can ask one local assistant about events from connected Google and Outlook accounts in OGAD (Off Grid AI Desktop). This is useful when your work schedule and personal schedule live in different services.
Use explicit dates, account names, and a display time zone. In this release, Google reads use the account's primary calendar. Outlook can list calendars and read a selected calendar. The workflow does not automatically include every calendar you can see in a browser.
Download OGAD | Desktop beta 122 release notes
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@getoffgridai.co, join our Slack community, or talk to us on Reddit.
Prepare the calendar connections
Install OGAD and open its Pro Integrations workflow. Connect Google and Microsoft, then complete the sign-in steps offered by your build. If the setup requests application details, provide the configuration required for that provider.
Give the connections useful labels. “Personal Google” and “Work Microsoft” are easier to refer to than two similar email addresses. Check that calendar access is enabled for each connection you want to use.
Select a local model that can use the account tools. The model can process event information locally, but fetching live Google and Microsoft events requires internet and a valid account connection.
Establish exactly which calendars are included
Ask the assistant to identify the available account connections. For Microsoft, ask it to list the calendars and identify the one you want. For Google, keep the primary-calendar limit in mind before you rely on a combined answer.
If a family or team schedule lives only in a secondary Google calendar, say that it is outside this guide's verified connector coverage. Do not assume it is included because it appears beside your primary calendar in Google's own interface.
Make a short scope statement in the conversation: “Use Personal Google's primary calendar and Work Microsoft's Team calendar.” That scope should appear in the result so you can see what was checked.
Ask for a date range with a time zone
Try a prompt such as:
List events from Personal Google's primary calendar and Work Microsoft's selected work calendar for 14 October 2026, from 00:00 to 23:59 Asia/Kolkata. Show start, end, title, source account, and calendar. Display every time in Asia/Kolkata. Keep all-day events separate. State any calendar you could not read.
Replace the date and zone with your own. A precise range avoids the ambiguity of “tomorrow” when an account, computer, or attendee uses another zone.
Ask for both start and end times. A start-only list cannot tell you whether an event overlaps another event or leaves enough time for travel.
Read the combined agenda carefully
Sort the result by time, while keeping the source account and calendar visible. Separate all-day entries from timed meetings. An all-day reminder may mean something different from a blocked workday; check its source before treating it as unavailable time.
Open a few events in their original calendar. Confirm the times and any recurrence details. An event series can have changed or cancelled instances, so the next occurrence matters more than the series title alone.
If the assistant reports no events, verify whether that means an empty date range, an unavailable calendar, or a failed read. Those are different results and need different next steps.
Ask useful follow-up questions
Once the agenda is correct, ask focused questions: “What is my first timed event?”, “Which event ends latest?”, or “Show gaps of at least 45 minutes between these meetings.” Keep the same scope and time zone in the follow-up.
Treat free gaps as candidates. A calendar cannot represent work you never entered, travel time you omitted, or another calendar outside the checked set. The assistant should not describe a candidate gap as guaranteed availability.
The direct calendar tools here read information. Asking about a possible meeting time does not create an invitation or move an existing event. Make any calendar change through a separately supported, reviewed action or the provider's app.
Troubleshoot the combined view
| Symptom | Check |
|---|---|
| A Google event is missing | Whether it belongs to the primary calendar |
| An Outlook calendar is absent | Calendar list, selected ID, and account permissions |
| Times appear shifted | Requested display zone and event offsets |
| Only near-future events appear | Explicit start and end bounds |
| A busy day looks empty | Connection errors and result limits |
Default reads cover a limited window, and results have limits. Google calendar reads in this release return at most 50 events per request. For a dense period, use a shorter range and check coverage rather than assuming a single response contains everything.
Make a reliable daily check
Save the wording that produced a correct agenda. Reuse it with new dates, or place it in a God routine after testing the manual result. A scheduled read still needs the computer, app, model, network, and accounts to be available.
Connect your calendars in OGAD and compare one day's combined list with the provider apps. Once that scope is correct, the same local conversation can become a useful starting point for planning your day.
Top comments (0)