A useful AI task should not need the same prompt every morning. OGAD (Off Grid AI Desktop) can run saved instructions on a schedule through God, its Pro assistant workspace. You set the task, choose when it runs, and return to the result in God.
The computer and app must be available. Local models can work with local sources after setup; tasks that read email, calendars, or websites also need those services to be reachable.
Download OGAD | Desktop beta 122 release notes
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@getoffgridai.co, join our Slack community, or talk to us on Reddit.
Choose a result you can check
Start with one repeated job: a morning agenda, a Friday work report, or a daily list of open decisions. Define what the output should contain and which sources it should use. “Keep me organized” leaves too much for the model to guess.
A better first task is: “At the start of each workday, list today's meetings and the open tasks due today. Include the source for each item. State when a source is unavailable.” That produces a short result you can compare with the underlying records.
A scheduled task is not a cloud worker that keeps running after you shut down the computer. Set its time for a period when OGAD and the required models will be available.
Prepare the sources before the schedule
Install OGAD and open God with Pro enabled. Select a local chat model that supports the tools required for your task. Download the needed models before expecting an offline run.
Connect the accounts you want the task to read. For saved activity, enable the relevant capture and memory features first. Capture is opt-in and has a visible state; it cannot reconstruct work that happened before it was enabled or after its records were removed.
Ask the task once in God chat. Check that it can read the expected calendar, note, or saved activity. A schedule will repeat the instruction, but it cannot repair missing source access by itself.
Add the recurring task
- Open God settings and expand Scheduled tasks.
- Choose Add a scheduled task.
- Enter a clear Name.
- In What to do, write the sources, date range, output, and limits.
- Choose When and set the relevant time or event.
- Choose Add and check that the task is enabled.
The supported choices include a one-time run, selected days at a local time, a repeating interval, and events such as a meeting approaching, an email arriving, a task finishing, or an action waiting for approval. Repeating intervals start at 15 minutes; this is not a second-by-second monitoring service.
For a weekly task, choose the intended weekday and local time. For an event, use a narrow match where available. A match is a text filter, so a short common word can select more events than you intended.
Test with Run now
Use Run now before you rely on the first scheduled run. Open the resulting conversation and inspect the content, sources, and any errors. A saved schedule and a completed job are different states.
For a morning agenda, compare two events against the calendar. For an open-task review, check whether the result distinguishes completed work from unresolved work. If the response fills gaps with guesses, edit What to do to require “unknown” for missing evidence.
Use Edit and Save to improve the instructions. Change one part at a time so you can see whether the new prompt fixed the actual problem.
Keep actions separate from summaries
Reading connected sources and drafting a brief can produce a useful result without sending anything. If a routine proposes an action that needs your approval, review that request in God.
A prompt such as “prepare a reply” should say whether you want a draft only. Do not assume that a summary means an email was sent or that a proposed task means another system was updated. Read the action state and any confirmation from the destination.
For your first routine, ask for information only. Once that works, add the next step deliberately and keep the scope clear.
Diagnose missed or incomplete runs
| Symptom | Check first |
|---|---|
| No result appears | Task enabled, computer awake, OGAD running |
| Output is late | Other model work and the local job queue |
| Calendar or email is missing | Account access and network availability |
| Activity summary is sparse | Capture settings, retained dates, and source coverage |
| Too many event runs | Event type and match text |
The scheduler checks for work periodically. Model jobs can wait behind other work, so a scheduled time is not a promise of an exact delivery second. Use a lead time that fits your task.
Build a routine you will keep
Turn a task off when you need to pause it; use Delete when you no longer want it. Review the first few results before adding more routines. A short schedule that produces a checked, useful output is easier to maintain than ten broad prompts that all search the same sources.
Open OGAD and schedule one repeatable job. Run it once now, check its evidence, then let the next scheduled run do that same defined piece of work.
Top comments (0)