When a client uses one email address and your team uses another, finding a decision can mean searching several inboxes. OGAD (Off Grid AI Desktop) lets a local AI assistant search connected Gmail and Outlook accounts from one conversation.
The account tools read the providers over the internet. The AI can run locally, but this is not offline email access. The released Gmail search returns message details and snippets; Outlook also has a tool to read an individual message as text.
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.
Connect the accounts you actually need
Install OGAD and use the Pro account-integration workflow. In Integrations, choose Connect for Google or Microsoft. Complete the offered sign-in flow and review the account and services you authorize.
Some installations use a configured hosted sign-in flow; others require your own application details. Follow the setup presented by your build rather than assuming every provider needs no configuration.
Add another account where needed and give each connection a clear label, such as “Studio Gmail” and “Client Outlook.” The label should tell you which mailbox a result came from. A connected provider name alone may not distinguish two accounts.
Test each mailbox before combining results
Select a local tool-capable model and open God or the chat workflow with the account tools available. Ask for one recent message from a sender you know, naming one account.
Check the returned sender, subject, date, and link. Repeat for the other account. If one connection cannot read mail, fix that before asking a broad question across both.
This small check catches common mistakes: signing into the wrong account, enabling calendar access without mail access, or assuming an organization permits a service that it has restricted. A successful provider login does not prove that every service is available.
Ask a bounded question across both accounts
Use a prompt that defines the people, dates, and evidence you want:
Search Studio Gmail and Client Outlook for messages about the Cedar launch between 1 and 12 October 2026. List sender, subject, date, account, and message link. Separate confirmed launch dates from proposals. If a preview does not show the full decision, mark it for review instead of inferring the missing text.
Use a date range that fits your own task. For Gmail, the search tool accepts Gmail query syntax, which can help narrow sender and date terms. A specific query is more useful than asking for “everything important.”
Ask the assistant to report which accounts it searched. If it used only one account, the answer is incomplete even if the prose sounds confident.
Understand the difference between a snippet and a message
The Gmail tool returns subject, sender, recipients, date, snippet, and a link. A snippet is useful for finding candidate messages. It is not a complete thread or a guarantee that the sentence you need is present.
Outlook search also helps identify candidates, and the released connector can read one selected message as text. Ask it to read the relevant message before quoting a decision that the preview does not establish.
For Gmail, open the returned link in Gmail when the full wording matters. Do not let the model turn a short preview into a claimed full-message summary. Attachments and linked documents require their own inspection.
Turn search results into a decision list
Ask for a table with issue, latest supported position, source date, source account, and open question. Keep proposals separate from accepted decisions. “Could we move Friday's review?” is not confirmation that the meeting moved.
Then inspect the newest relevant message and any earlier message it refers to. A later timestamp alone does not guarantee a superseding decision; it may be an unrelated reply in the same thread.
If two accounts contain copies of the same exchange, retain one decision entry with both references where useful. Do not count duplicates as independent confirmation.
Fix missing or incomplete results
| Problem | Next check |
|---|---|
| One mailbox is absent | Connection label, enabled mail service, and account scope |
| Older messages are missing | Date range and query terms |
| Only recent inbox mail appears | Explicit search query instead of a default inbox request |
| A claim exceeds the preview | Open Gmail or read the Outlook message |
| Too many results to review | Narrow by sender, topic, and shorter periods |
The tools have result limits. Gmail search returns up to 20 messages per call in this release. A single result set is not proof that the entire mailbox was searched exhaustively. Split a broad search into useful periods and inspect the tool results.
Keep the privacy claim precise
With a local model selected, the returned message content can be processed on your computer. Gmail and Outlook remain online services, and their account APIs are used to fetch the data. Selecting a remote model changes where the prompt and retrieved material are processed.
The direct email tools described here are read-only. Finding a message or drafting a response does not send an email. Review and send through a separately supported action or your normal mail app.
Connect two accounts in OGAD and search for one decision you already recognize. Once the sources and account labels are correct, use the same bounded approach for the next client question.
Top comments (0)