You remember the detail but not where it appeared. It could be in an AI chat, a meeting transcript, a document or a screen you saw yesterday.
OGAD (Off Grid AI Desktop) Pro brings those retained sources into one Search view on your Mac. Start with a phrase or topic, narrow the source, and open the matching record. You can find the evidence without first remembering which app or conversation held it.
| Download OGAD for Mac | Beta 0.0.52-beta.103 |
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.
What can this search find?
Search covers material OGAD has saved and indexed. That can include its own chats, project documents, meeting text and opted-in screen activity. It is not a search of every file or page on the computer.
| Remembered detail | Possible source to check |
|---|---|
| A phrase from your AI discussion | Chat |
| A decision from a recorded call | Meeting text |
| A requirement in a supplied PDF | Project documents |
| Words visible in another app | Retained screen activity |
The linked beta combines keyword matches with semantic results when a local embedding model is ready. Keyword search can still return results without that model. A source must exist before either route can find it.
Start with the words you remember
Open Search and type a distinctive phrase, project name or subject. Start with two or three useful words rather than a long sentence with several unrelated conditions.
Try “workshop venue” if you remember a venue decision but not the conversation. Check the source labels and snippets. Choose a source under Sources if you want to narrow the results, or use clear to remove that filter.
Use Relevant for the initial search, Recent when time is the better clue, or Match to compare the query matches. Enter a query first; an empty search should not be treated as a complete recent-activity feed.
Open the source before you act
A result is a route to supporting material, not a new authoritative answer. A chat result opens the conversation; a recorded-meeting result leads to meeting material. Screen-history results can open Replay. Project-document results can open the related project chat rather than the exact paragraph in an external editor.
Check the content and date. An earlier discussion may have been replaced by a later decision. If you are about to send a deadline or quote a requirement, read the relevant source first.
Add useful sources deliberately
OGAD chats and documents you add to a Project provide deliberate material. Meeting records need a recording and successful transcription. Screen history begins only after you enable Pro capture and confirm the visible Capturing state.
For screen history, prepare local processing and required permissions, then use Resume capture in Replay or Capture settings. Pause it for sessions you do not want retained. Search cannot recover screens from before capture or records removed by retention.
Search data you imported from connected apps
A connected account is not the same as an imported local record. In Integrations, open a supported, connected service and use Sync recent, or enter a supported query and choose Pull. Wait for the import result before returning to Search.
Use a distinctive term from the imported material, then narrow Sources to the service when that source is available. Check the saved snippet and the original service before treating the result as complete or current. An import can contain summaries or limited text rather than every message and attachment.
The connection and import need the service’s network access. Once data has been retained locally, Search can use that saved material. It does not make a fresh search of every connected account each time you type.
When a result is missing
Try an exact name or short phrase, remove a source filter, and check whether the original record still exists in its own view. If a meeting transcript is missing, complete that processing before expecting transcript search to work.
Local search and local model selections can keep the analysis on your Mac after setup. Connecting external sources and refreshing their data have separate network needs. Remote model selections also change where processing happens.
Resolve a detail that appears in more than one place
Suppose a workshop date appears in a project document and a later recorded call. Search for the workshop name first, then inspect the source labels. Open the document result and the meeting result instead of assuming the first result is the latest decision.
Check the wording and date of each source. The document might be a proposal, while the call contains an agreed change. If the recording says only that a change was suggested, do not turn that suggestion into a confirmed date.
Once you have the checked facts, use them in your next task. You could paste the relevant passages into a local chat and ask for a short update that separates the original plan from the confirmed change. The search result helps you find the evidence; you decide which evidence supports the message.
Use source filters to answer different questions
If you need the exact wording you gave the model, narrow to chat. If you need to recover a visible page, inspect screen activity and Replay. If you remember a spoken decision, start with meeting text. Clear the filter when your first guess about the source is wrong.
Try a second query when the terminology changed. A client may call the same event a workshop, session or review. Use a short distinctive name before combining several terms that may never appear together.
A useful first test is a harmless phrase you deliberately placed in a saved chat and a project document. Find both and open them. That verifies the sources you actually have, rather than treating a connected account or a visible file elsewhere on the Mac as already indexed by Search.
Try OGAD for Mac with a phrase you know exists in two saved sources. Find both, open them, and compare the context before you use the answer.