Pending AI actions are easier to review when you can see what each one would do and why it was proposed. OGAD (Off Grid AI Desktop) can prepare a daily brief in God that reviews the actions waiting for your approval.
The brief is part of the Pro routine workflow. It does not grant approval. Read the actual action card and its current details before you approve or deny an action.
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.
Separate a to-do from an approval
An open to-do describes work that needs attention. A pending approval describes something the assistant proposes to do through an action. They may relate to the same project, but they are not the same state.
For example, “Reply to the client” can be a to-do. A proposal to send a particular message to a particular recipient is an approval item. The latter needs review of the actual destination and content.
Ask the daily brief to keep these categories separate. Otherwise, an ordinary task list can obscure which items would cause an external change if approved.
Prepare one real review source
Install OGAD, enable Pro, and open God. Check the current pending-action area and the separate approvals view in Actions where available.
Start with an item you recognize. Read its destination, requested effect, and source context. You do not need to create a risky action merely to test the brief; use an existing pending item or a harmless draft proposal you intend to review.
Select a local tool-capable model if you want local analysis of the available action context. A live account or external service can still require internet for its own data and execution.
Write a brief that supports a decision
Use a prompt such as:
Review actions currently waiting for my approval. For each, show the proposed action, destination, reason, and any missing detail that prevents a decision. Keep ordinary to-dos separate. Do not approve, deny, send, or modify anything. If an item is no longer pending, do not present it as awaiting approval. End with the items I should inspect first and explain the ordering.
This keeps the result descriptive. The assistant can help organize your attention, but it should not convert a high-priority label into your authorization.
If your work spans several clients, ask the brief to group items by client or project. That makes it easier to spot a proposal that uses context from the wrong account.
Add a daily schedule
Open God settings, expand Scheduled tasks, and choose Add a scheduled task. Set a clear Name, add the instruction in What to do, and choose your review days and local time under When.
Choose Add, leave it enabled, and use Run now to inspect the first brief. Keep the computer awake with OGAD running at the scheduled time. A queued model job can delay the result.
There is also an event choice for When something waits for my approval. Use that when you want a response to new pending items. It is different from a daily review of the current queue; choose the trigger that matches your routine rather than enabling both by accident.
Review the actual action card
For each item you decide to handle, return to its current action card. Check the recipient or destination, the content or change, and the account through which it would run.
Use Ask Ares, or the equivalent control for your selected assistant name, when you need more context. Use Approve or Deny only after reviewing the current proposal. The morning brief may be older than the action's latest state.
If an approval causes an action to execute, inspect its result. Approval is your decision to let it proceed; it is not proof that the destination accepted the operation or that execution succeeded.
Handle stale and duplicate proposals
A proposal can become unnecessary because you completed the work yourself or another event changed the plan. Check the latest source before approving an old item simply because it appeared in the brief.
If two items appear to propose the same change, compare their destinations and contents. Do not approve both until you establish whether they are duplicates or separate intended actions.
Ask the brief to flag possible duplicates as candidates for review. It should not silently delete or deny them based only on similar wording.
Fix an unhelpful brief
| Symptom | Better next check |
|---|---|
| To-dos and approvals are mixed | Require separate sections and current states |
| Destination is unclear | Inspect the action card before deciding |
| An old item is still listed | Recheck the live pending state |
| Routine does not run | Enabled state, awake computer, and model queue |
| Ordering feels arbitrary | State your deadline and project priorities |
A useful brief makes missing information visible. If the assistant cannot establish what an action will do, the output should say that review is incomplete instead of recommending approval anyway.
Make the review a short daily habit
After the first few runs, use Edit and Save to keep the grouping and level of detail that helps you decide. Keep the no-action instruction in place if your aim is a review brief.
Schedule a pending-action review in OGAD and compare its first result with the actual queue. Use it to choose what to inspect, then make each approval decision from the current action details.
