A client portal shows today's request. OGAD (Off Grid AI Desktop) may already hold the earlier meeting or work note that explains it. The browser extension's Agent route can use available desktop memory so you can compare the current page with that retained context.
This is useful for a question such as “Does this request match what we agreed?” The answer depends on what was actually saved. Screen capture remains optional, and the assistant cannot recover work that was never retained or supplied.
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.
Give the comparison a clear purpose
Suppose a portal now asks for four deliverables, but you remember discussing three. You need the earlier agreement, the current request, and the specific difference. A general project summary could miss that conflict.
Ask for a comparison with separate source columns. The current page is one source. A saved meeting transcript, note, or captured work item is another. Keeping them separate stops an old statement from being presented as the current portal state.
The same method can help with an earlier decision, a promised follow-up, or the reason a team chose one approach. It works best when you provide the project name and an approximate date.
Prepare retained context on the desktop
Use OGAD Pro with the saved work you want to reference. Confirm that you can find one relevant item on the desktop before you ask the browser to use it.
If you want screen activity available for future questions, enable capture deliberately and check its visible state. This does not create a history of work done before capture was enabled. Excluded applications and deleted records will also limit later answers.
Use a local text model with tool support. The model needs to retrieve and read context rather than answer entirely from its own training. A local model keeps that model processing on the desktop; a remote model may receive the retrieved text.
Ask from the browser
- Install the early-access extension and pair it with OGAD.
- Open the relevant portal page in the browser where you are signed in.
- Select Agent in the extension's composer controls.
- State the project, the approximate date of the earlier discussion, and the comparison you need.
- Ask for reading only if you do not want changes to the website or another account.
Try this:
Compare the deliverables on this page with my saved notes from the Northwind review last week. List each added, removed, or changed requirement. Give the current page text and the saved source for every difference. Do not change the portal or send a message.
Replace the example project name and date. A narrow search is easier to verify than a request to use everything the assistant knows about your work.
Review the evidence before the conclusion
Open the saved source for the first claimed difference. Confirm that it refers to the same project and that the speaker had actually agreed to the requirement. A suggestion in a meeting is not necessarily an approved change.
Then check the portal. It may show a draft, an old revision, or a status that has not yet been updated. Ask the assistant to state those uncertainties instead of choosing the newest-looking sentence automatically.
| Comparison item | Evidence to retain |
|---|---|
| Earlier agreement | Note or meeting name, date, and supporting passage |
| Current request | Page URL, field or section, and current wording |
| Difference | A short description of the change |
| Next step | A question to resolve, or an action for your review |
This gives you a useful basis for a client conversation. It does not prove that the client has approved a change simply because two records disagree.
Use the answer to draft a careful follow-up
After checking the comparison, ask for a draft that names the difference without assuming blame. For example: “The portal includes a fourth deliverable. Our review note lists three. Can you confirm whether the fourth is part of this phase?”
Keep the draft in the conversation for review. Sending it is a separate action. The useful automation here is finding and comparing the evidence while you remain beside the live request.
When the old work cannot be found
Check the project name, date range, and source type. Try a distinctive phrase from the earlier discussion. If the record is absent, supply the note you have or say that the earlier agreement remains unverified.
A failed search is not proof that no agreement existed. It may mean the relevant application was excluded from capture, the recording was not retained, or the wording differs from your search.
The browser connection also does not silently capture every tab for future memory. Current page context and retained desktop work are separate inputs. Keep that distinction in mind when deciding what the answer can support.
Use OGAD with one saved decision and one current page. Verify both sources, then draft the question that resolves the difference.
Top comments (0)