On this page
You can leave your desk and still check a computer AI task from your phone. OGAM (Off Grid AI Mobile) Pro can show the task’s progress and available screens, send a correction to the execution computer, and request a pause or stop. OGAD (Off Grid AI Desktop) continues to do the work.
Use paired, reachable devices with Pro sync. A request on the phone is not complete until the desktop confirms it. The phone does not become a remote mouse for the computer.
| Download OGAD | Get OGAM |
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 [email protected], join our Slack community, or talk to us on Reddit.
Pair the workspace before starting the task
On OGAD, open Devices. In OGAM, open Settings → Sync and pair the phone with the computer using the displayed QR code or pairing-code flow. Check that the same conversation appears on both devices.
Pairing shares the supported workspace data, including chats and projects; it is not a one-conversation-only sharing switch. Use devices that you intend to connect to that workspace.
This guide covers the OGAM beta 114 release with a compatible current desktop release. Prepare app downloads, models, and Pro access before you depend on local use.
Start a task with a clear result
Choose a small Web Use or Computer Use task on the desktop. For example, ask it to compare two pages and return a source-linked table. Confirm that the task has started before you leave the computer.
Open that synced conversation in OGAM. Find the task card and check Runs on. It should name the computer you expect to execute the task. A card from an earlier run is not evidence about the current one.
Keep the execution computer awake with the app running. The phone can display and control a task through the connection, but it cannot keep a sleeping computer doing work.
Read progress and screens together
Check CURRENT ACTION and the recorded Activity. Compare the described action with the available current screen or saved steps. Use the session replay when it is available to inspect earlier points in the run.
A saved frame is one captured moment. It is not continuous video of every action. If the card is waiting for the current screen, give the devices time to reconnect before treating the last visible frame as live.
For a page comparison, check whether the task is reading the intended pages. For a file edit, use the phone to follow progress, then inspect the actual saved file before you share it. A completed status does not prove the output is correct.
Send a correction while the task is active
Use GUIDE THIS TASK to add a detail or correct the instruction. Enter a short, specific message, then choose Send guidance.
For example: “Use the annual price, and include the source URL beside each number.” That changes the task’s direction more clearly than “do it better.” The phone reports when the execution device accepts the guidance.
Guidance goes to the named execution device and is not saved in synced task history. Acceptance means the message reached the task path; inspect later activity and output to see whether the requested correction was carried out. Completed tasks no longer show the guidance composer.
Pause, continue, or stop with confirmation
The task card shows the controls appropriate to its current state. Use Pause to request a pause, the available resume or Continue control when appropriate, and Stop when you want the task to end.
After tapping a control, read the pending state and wait for the desktop’s confirmation. The app can report a rejection or a timeout if the desktop does not confirm within 15 seconds. Do not treat “Stop requested” as proof that execution has stopped.
If the task is waiting for a step that requires you on the computer, complete that step there and then use Continue on the phone. The phone preview does not take control of the Mac to perform that handoff.
Handle lost connections
| Symptom | Next check |
|---|---|
| Entire conversation is absent | Workspace pairing and chat sync |
| Progress is stale | Execution device connection and awake state |
| No saved session appears | Whether this run has available captured steps |
| Control request times out | Desktop availability and actual task state |
| Guidance is accepted but result is wrong | Subsequent activity and final output |
If the computer goes offline, progress and controls resume when the connection returns. The last known card can still be useful history, but it is not confirmation of current execution.
A local network can carry device communication without internet. A task that reads online websites still needs internet. Access from another location requires a suitable remote route and its own connectivity; it is not the same as offline use on home Wi-Fi.
Test the control path before relying on it
Try one harmless reading task while you are still near the computer. Open its card on the phone, send a small correction, and test a pause or stop. Compare the phone’s confirmation with the desktop state.
Connect OGAM and OGAD and complete that small check first. You can then leave the desk with a clear way to inspect progress and request an intervention, while the execution computer remains responsible for the work.