You promised to send a draft in one chat and review a file in another. By the afternoon, both commitments are buried under newer messages.
OGAD (Off Grid AI Desktop) Pro can extract concrete to-dos from work-chat text captured on your Mac. After you enable screen capture and prepare local models, background processing can add those commitments to Actions. You review one list instead of relying on your memory of every conversation.
| 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 gets added automatically?
The extractor looks for a clear request or commitment with a next step. “I will send the draft by Friday” is a useful candidate. A general discussion about improving a draft might not be a task at all.
OGAD processes new captured communication, rather than importing your complete message history. Capture is sampled, scans are limited, and the model can miss or misread a commitment. A to-do is a suggestion to review, not proof of what you agreed to do.
This guide uses the Mac Pro workflow in the linked beta. Keep the capture analysis and text-model choices local for local processing. Prepare downloads and Pro access while connected.
Start with one work-chat commitment
- In Models, prepare and select a local text model. Use local capture processing too.
- Allow the required screen and Accessibility permissions in Settings → Setup & health → System permissions.
- Open Replay or Capture settings and choose Resume capture. Check the visible Capturing state.
- Use a work chat you intend to capture. Leave a concrete commitment visible during your normal work.
- After processing, open Actions → To do → open and check for the suggestion.
You control when screen capture runs. Use Pause capture when you do not want a session retained. This workflow can use text visible in another app; it does not require sending that app’s full account history to OGAD.
Check where a to-do came from
Select an extracted task’s text to expand Where this came from. The source card can show the application, time and source summary. Compare that context with the original conversation before relying on the owner or deadline.
If a task has a person or project label, select the label to filter the list to that record. Use clear to return to the full list. Labels are inferred links, so an empty filtered list does not prove that a client has no outstanding work.
This is useful before a client call: collect the linked tasks, then check which ones are still open and which details need confirmation.
Add the commitment the model missed
Use the Jot a to-do field at the top of Actions. Write one concrete line, such as:
Send the revised workshop outline to Maya by Friday.
Press Enter or Add. The raw task is saved immediately. The model can then infer a priority and due date in the background. Check those fields; relative dates and names can be misunderstood. Your manually entered text remains useful if enrichment fails.
Keep the list useful
Mark completed work done. Use Dismiss for an incorrect or irrelevant suggestion; you can give an optional reason. The dismissed tab lets you find the item again and Restore it if needed.
Do not use Done to hide a task that was never yours. Separating completion from dismissal keeps the list easier to review.
Actions → To do holds commitments. It is different from Tasks, which holds AI agent runs, and from Approvals, where proposed external actions may need review. A saved to-do does not send a message or carry out the work.
Turn a normal work session into a checked action list
For a first useful session, choose one project chat you already use. A clear commitment might be: “I will send the revised outline to Maya by Friday.” A second message might ask you to review a file before a call. Work normally with capture enabled for that session, then open Actions after processing.
For each suggested item, compare three details with the original conversation: what needs to be done, who owns it and whether a deadline was actually stated. Keep the source beside you while reviewing. A task without a stated date should not acquire an invented one simply because a date would make the list look complete.
If the outline task appears correctly, you no longer need to retype that commitment into a separate planner. If the review task is missing, add it with Jot a to-do. The practical result is one checked list assembled from both background extraction and the details you supply.
Build a short review into the end of the session
Open the project or person filter and scan the related open items. Mark work you actually completed done. Dismiss a general discussion that became a false task. Keep an unclear item open only after you have established what it means.
You can then ask a local-model chat to help draft a message using a task’s checked facts that you copy into it. For example: “Draft a short note sending the outline for review. Do not claim approval or a delivery date that is not in these facts.” Review and send it yourself.
Background collection reduces the repeated work of noticing and copying commitments. The short review is where you turn those suggestions into a list you can trust for the next work session.
Try OGAD on your Mac with one short captured work session. Review the source behind each suggested task, add anything missing, and finish with a list you can actually act on.