A routine Windows job can mean the same sequence of clicks and typing every time. A local AI assistant can do a small, well-defined sequence while you watch. 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.
Use the Windows installer, with a visible desktop session and the target app open. Computer Use depends on the native input component included in the build. If OGAD reports that screen control is unavailable, resolve that problem before trying a larger job.
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 Notepad 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 Notepad. 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 Notepad.
- 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.
Write the task as a visible end state
Computer Use works from the apps and controls it can inspect. A useful brief names what should exist when it stops, rather than describing an open-ended goal such as “organize my work.”
For the Notepad example, you can check the result without judging a long chain of hidden reasoning: the correct window contains the heading and the requested sections, and the document remains unsaved.
Use this brief shape for your next task:
| Part | What to supply |
|---|---|
| Target | The exact app and document |
| Starting state | A new blank file or a specific existing view |
| Change | The text or small action you want |
| Boundary | What should remain unchanged |
| Finish | Where it should stop and what you will inspect |
For example, prepare a new meeting-note template with Date, Attendees, Decisions, and Next actions. Ask it to leave the fields empty and stop before saving.
Check the app before reusing the brief
A task that succeeds in a blank document may need a different instruction in an existing one. The cursor may be in the wrong place, a dialog may cover the editor, or an old selection may change what typing replaces.
Pause before adjusting the app yourself. Restore the intended starting state, then continue with a precise instruction. Avoid competing with the assistant for the mouse while it is selecting a control.
If the task fails, read its saved steps and inspect the actual document. The last reported failure may occur after some text was already entered. Starting the same request again without checking can duplicate that work.
The benefit of a small first task is a reusable pattern you understand. Once you know the app, starting state, and stopping point, you can change the content while keeping the same clear structure.
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.
Download OGAD and try the three-heading document. Check that first result, then give it the next small part of your routine.