You repeat a short set of app steps every week: open a document, enter the same headings, and prepare it for review. OGAD (Off Grid AI Desktop) Pro lets you describe the target result and use Computer Use to work in visible apps. Select local models to keep the AI reasoning on your computer. The app you control may still use the internet.
| Get OGAD | Current desktop release |
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.
A good first task has a clear end: make a draft, fill a few fields, or prepare a document. It should be small enough that you can check the result quickly. Start with a new sample document before using an important file.
What do you need?
Use OGAD with Pro active and a downloaded local text model. Computer Use can also use a downloaded specialist model to choose screen targets. In Models, prepare a supported Computer Use model, then select it as the Grounding specialist in Settings > Computer use. Use Reasoning + Specialist for the Computer Use model strategy with Vision enabled.
In Settings > Setup & health > System permissions, grant Accessibility and Screen Recording access. Relaunch OGAD if requested. These permissions let it inspect and operate your Mac.
Keep all selected task models local for local inference. Choosing a remote model changes where the task context is processed.
Make one useful document
- Open TextEdit and create a new, empty document.
- Open an OGAD chat and turn Assistant on.
- Ask for the following small task, changing the text if useful:
Use Computer Use in TextEdit. In the new empty document, enter a heading called Weekly review. Under it, add three headings: Finished, Next, and Blocked. Put one blank line below each. Stop when the text is visible. Leave the document open and unsaved.
- Watch the task as it runs. When it finishes, check the text in TextEdit.
- Save the document yourself if it is correct.
The expected result is text in the app, not just an answer describing what to type. If the assistant only explains the steps, check that Assistant is on and ask it to use Computer Use in the named app.
Watch, pause, and take control
The task controls include Pause, Stop, and Take Over. Pause before you change the screen yourself; use the resume control after you have checked the task state. Esc can stop the task when that shortcut is available. The visible Stop control remains the direct option.
Open Tasks to review the run and its saved steps. A saved task record helps you see what it attempted, but it is not a guarantee that each change succeeded. Check the document itself.
Use the small supervisor window
Computer Use has a floating supervisor so you can keep the task status and stop controls visible while OGAD works in another app. In 0.0.52-beta.102, the window can collapse to take less space. Use Collapse PiP or Expand PiP on that window. Under Settings > Computer use > Computer Use, Picture in Picture controls whether it appears during tasks.
The smaller window does not give the AI a separate mouse and keyboard. Read another screen or monitor progress, but pause or take over before you interact with the app it is controlling. Hiding the window is not the same as stopping the task.
When should you use Accessibility and Vision?
Under Settings > Computer use, Enabled rails lets you choose Accessibility, Vision, or both. Accessibility uses the controls that an app exposes; Vision helps with the visible screen. Grant the required Mac permissions before either route needs them.
Keep the Vision setup above for the first sample. If an app exposes useful accessible controls, you can try both routes, then check the result with the same short task. The selected model strategy affects which route leads: with Reasoning + Specialist, Vision can lead while Accessibility supplies control details. The Decider strategies require Accessibility and use Vision for recovery. Do not assume every strategy has the same order or that every app exposes usable controls.
The collapsible window and the newer strategy behavior above refer to 0.0.52-beta.102. That beta also makes task tools available without Pro. The main setup steps in this guide use the stable release’s Pro Assistant path.
Make repeated work easier
Once the small example works, reuse the same brief with different document content. Name the app, starting state, exact text, and stopping point. For example, ask for an empty client-review template before asking it to fill real client information.
This is automation that you start with a request. It does not create a scheduled recurring job by itself. Leave the computer awake, keep the target available, and avoid using the mouse at the same time.
If the model selects the wrong control, stop and reduce the task to one action. If it cannot find a window, bring that window into view. If a model cannot load, choose one that fits the available memory.
Start from a prepared workflow
In OGAD 0.0.52-beta.103, open Assistant to choose a prepared workflow. Fill in its requested details, then select Start in chat. You can give the task a specific brief without writing the whole instruction from scratch.
Choose a task you can review easily, such as preparing an email reply. Supply the message and the points you want in the draft. Review the required fields before you start, and check the draft before you send it. A prepared workflow still needs its required models, permissions, and any app connection. A web task still needs internet access.
Return to a task and inspect its result
Open Tasks and select the run from Task history. The list shows its state and recorded steps. In the detail view, Show screenshots and Show decision details let you inspect the available record. Use Open the chat this task came from when that control is offered to return to the original conversation.
This is useful when you return after the task has finished or need to see where it stopped. Check the actual document or app as well as the saved task record. A completed status does not replace checking that the requested result is correct.
Add a correction while the task is running
In the beta.103 task detail view, a live run can show Guide this task…. Type a short correction and send it. For example: “Keep the existing heading. Change only the first paragraph.” Wait for the guidance result before assuming it was accepted.
Use this control on the computer running the task. If it says guidance is unavailable, follow the message shown for that run. A finished task cannot accept a live correction.
Guidance changes the remaining instructions; it does not undo an action already completed. Use Pause or Stop when you need to prevent further work, then inspect the current app state. Keep the correction specific so you can check the next result.
Download OGAD and try the three-heading document. Check that first result, then give it the next small part of your routine.