On this page
A repeated task can involve the same clicks and text across several apps. OGAD (Off Grid AI Desktop) Pro beta 114 includes Linux Computer Use. Give it a small job, follow its visible progress, and check the result before you use it.
| Download OGAD | Get beta 114 |
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.
Choose a task with a clear finish
Start with a harmless job in a test document. For example, collect three headings from an open document and make a short checklist in a blank note. This checks reading, app navigation, and text entry without depending on a long chain of changes.
Computer Use works with visible desktop apps. Web Use is a separate browser route. If all the work is reading web pages, use Web Use rather than asking the assistant to drive unrelated desktop windows.
A clear brief names the app, the input, the output, and the point where work must stop. “Organize my computer” does not supply those details. A small task is easier to check and easier to resume after a failure.
Prepare the Linux beta and models
Use the x64 Linux AppImage or deb from beta 114 with Pro active. Prepare a local tool-capable text model and any compatible local vision or specialist models required by your selected strategy.
Review Settings > Computer use and inspect the Computer Use model strategy. Local reasoning requires local selections for the processing steps you use. A local chat model alone does not make a separately selected remote specialist local.
Linux accessibility uses information exposed by the desktop and applications. Screen capture and simulated input also depend on the session. On Wayland, portal access and compositor restrictions can affect the route. Check an ordinary app before assuming every custom control can be operated.
Try a short visible task
- Open a harmless source document and a blank destination note.
- In OGAD chat, turn Assistant on.
- Give a Computer Use brief that names both apps.
- Follow the task in Tasks.
- Stop the run if it moves outside the intended windows.
- Check the destination against the source.
Try this:
Use Computer Use to read the three section headings in the open test document. Put those headings, in order, into the blank note as a checklist. Do not change the source document, open other files, or send the note. Stop after the checklist is ready.
The expected result is three matching headings in the destination. Compare spelling and order. The test document supplies the facts; the model should not invent a fourth heading.
Read the task progress
Visible progress helps you see whether the task reached the right window and control. A run that is still active has not necessarily completed useful work. Watch the destination as well as the task status.
If a control cannot be found, keep the verified part of the result. Open the missing section yourself or simplify the task. Repeating the same broad brief can reproduce the same failure.
A browser or desktop app can show content that tries to redirect an assistant. Keep your original task boundary clear. Source text does not grant permission to visit another account or send a message.
Expand only after the first result works
Once the checklist is correct, try another small task in the same apps. You might copy a set of checked dates into a note or prepare a draft from visible source text. Keep one useful output per first run.
Tasks involving accounts, submissions, or important files need a precise brief and review of the action. Do not use a successful harmless test as proof that an unrelated app can be operated reliably.
What if input or capture fails?
Check the session’s system access, active window, and the selected models. If accessibility text is unavailable, a compatible visual route may be needed. If simulated input is blocked, resolve that session limitation rather than assuming another prompt changes it.
Local inference does not make an online app offline. Websites and connected services still use their normal network paths. Initial model downloads also need internet. A locally prepared note remains a draft until you check it.
This guide covers OGAD beta 0.0.55-beta.114. The release and build record identify the desktop version and its included Pro code. Setup details follow that code; they are not a device test.
Get the Linux beta, prepare Pro, and try one three-heading checklist before assigning a longer desktop task.