You want to check your schedule and add an appointment in the same conversation. OGAD (Off Grid AI Desktop) can use your Mac’s Calendar tools with a local model. When your Google account is connected to macOS Calendar, this gives you a route to read its events and create an event in that Google calendar.
| Get OGAD | Desktop releases |
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@offgridmobileai.co, join our Slack community, or talk to us on Reddit.
This guide uses native Mac Calendar access in the core app. It does not require the separate Google OAuth client setup in OGAD. Google account sign-in and calendar synchronization need internet access.
Add your Google calendar to the Mac
In the Mac Calendar app, choose Calendar > Add Account, select Google, and finish sign-in. Check that the calendar you want is visible and writable. Apple’s calendar account guide explains this account connection.
Use a distinct calendar name so that OGAD can select the right one. If several accounts have a calendar with the same name, resolve that ambiguity before asking the AI to create an event. The native creation tool matches a calendar by its name.
Check a time, then create an event
- Select a downloaded local model in Models > Text.
- Open a chat and make sure Tools is on.
- Ask it to list events for a specific date range and timezone. Allow macOS Calendar access if requested.
- Review the returned events and the calendar names. Choose a suitable time.
- Ask for the exact event you want:
Create an event in my calendar named Work Google called Design review on 8 October 2026 from 14:00 to 14:30 Asia/Kolkata. Add the note: Review the navigation mockups.
- Open Calendar and check the event’s calendar, date, start, and end. Confirm that it appears in Google Calendar after account sync.
Replace the example calendar name and date with yours. A create request can execute directly from chat, so include the final details before sending it.
Keep the right calendar selected
If the supplied calendar name is not found, the native tool can use the default calendar. That makes the final check important: a correctly worded event in the wrong account is still wrong for your workflow. Use an exact, distinct name and inspect the saved result.
Listing events may include other calendars available on the Mac. Ask for calendar names in the answer rather than assuming every result belongs to Google.
Use one conversation to plan a real appointment
A useful first task is scheduling a review around events that are already on your calendar. Ask for a narrow time window and the calendar names, then select the time you want to use.
For example:
List the events available to my Mac on 8 October 2026 from 13:00 to 17:00 Asia/Kolkata. Include the calendar name beside each item. Do not create or change anything yet.
Once you have checked that answer, give the final create request. Include the exact Google calendar name and the duration. This separates schedule inspection from the action that saves a new event.
If the returned list is unexpectedly empty, compare it with the Calendar app before treating the whole afternoon as free. The model can only use calendars available through the Mac’s native Calendar access. It does not automatically inspect every Google account you have ever used.
Check both the local save and the account sync
There are two results to verify:
| Check | What it establishes |
|---|---|
| The event exists in the correct calendar in the Mac app | The local Calendar operation reached the intended destination |
| The same event appears in Google Calendar after sync | The change reached the account you plan to use elsewhere |
These checks matter when you will join from a phone or share a calendar with someone else. Seeing a local event is not proof that another device has received it yet.
Do not create a second copy merely because the browser has not refreshed. Check the account’s connection and sync first. If the event is in the wrong local calendar, correct that in Calendar and verify the final location.
The create tool supports ordinary event details, but it does not supply every scheduling field. Use the Calendar app to complete invitees, recurrence, or meeting-link details when the tool does not expose them. A saved personal event is not evidence that other people received invitations.
Keep local AI separate from cloud calendar storage
The useful benefit is that a downloaded local model can interpret your request on your Mac. Choosing Google as the event’s destination still means using a Google-backed calendar.
If you need a calendar that stays only on the Mac, choose an appropriate local calendar instead and verify its destination. Do not describe an event stored in a Google account as having no cloud storage simply because its AI processing was local.
What about the Google integration in OGAD?
The separate Pro Google Calendar connector can read events from the primary Google calendar. Its current built-in tool is list_events; it does not create events. The native Mac Calendar route above is how this guide adds the new item.
A local model does not remove Google’s role in storing and syncing its calendars. Changes made while disconnected may need a later connection before they appear on another device.
Get OGAD, connect your Google calendar to the Mac, and try one clearly named event. Check it in both Calendar and Google before using the workflow for the rest of your schedule.