A long page can hide the detail you need. The Off Grid AI browser extension can send its readable text to OGAD (Off Grid AI Desktop) and produce a summary beside the source. Use a local text model to process the extracted text on your computer.
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 useful summary has a purpose. Before asking, choose whether you need the main argument, setup requirements, policy conditions, or questions for further research. This tells the model which details to retain.
For a technical guide, ask for requirements and the order of work. For a policy, ask for deadlines and exceptions. For an opinion article, ask for the author's claim and the evidence offered. These are different outputs, even when the source page is the same.
The extension needs Node.js 20 or later for a source build. It is not listed in the browser stores in this setup. Down the source and dependencies needs internet.
git clone https://github.com/off-grid-ai/browser-extension.git
cd browser-extension
git checkout 970fec49e2a630a3e1f419c1fc86df241891d40c
npm install
npm run build:chrome
In Chrome, open chrome://extensions, enable Developer mode, select Load unpacked, and choose dist/chrome. Start OGAD and select a downloaded local text model. Open the extension from the toolbar. Its default desktop connection is http://127.0.0.1:7878/v1 on the same computer.
For shared chats, desktop tools, or Vault, open the extension's Settings > Desktop and select Pair with desktop. Check that the six words match the dialog in OGAD, then approve there. A running gateway and an approved pairing serve different purposes.
The pinned extension source includes the browser connection used here. Later source changes can alter the setup.
Try this on a public setup guide:
Summarise this guide for someone preparing a first installation. Give the goal, required tools, main steps, and important limits. Keep required and optional items separate. Mark any missing version requirement as not stated.
You should get a compact reading aid. You should still use the original guide for commands and exact settings. A summary can omit a small condition that matters to your setup.
Read the source beside the answer. Check versions, dates, numbers, exceptions, and any statement that says a step is optional. A summary that removes “only on supported hardware” changes the meaning of an instruction.
Suppose a product page says one plan includes a feature and another offers it only as an add-on. Ask for those conditions in separate rows. Do not let a broad feature list hide the plan requirement.
Ask a focused follow-up when a claim is unclear:
Which sentence on the page supports the requirement in your second bullet? If the extracted text does not support it, remove that bullet.
The model may not receive all page content. Navigation, forms, and other surrounding material are removed during extraction. Content inside a closed section or another page may be missing. Open the section or supply its text rather than asking the model to invent a complete picture.
Use page supplies readable text. A screenshot supplies a visible image and requires a compatible vision model. Use text for a long written policy. Use a screenshot when the question depends on a visible chart or interface that text extraction did not retain.
Do not assume that a text model can read an attached screenshot. The extension offers screenshot input only when the model reports image support. Check the model before changing how you provide the source.
Save the checked summary with the page title and address. If the page has a publication or revision date, retain it. This lets you tell which version you read when the website changes.
For several pages, use a new chat or clearly identify each source. Keep conclusions linked to their source instead of asking for an unsupported ranking. A short comparison with missing fields marked can be more useful than a long answer that hides gaps.
The selected local desktop model performs inference. Fetching an online page still needs internet. App and model downloads also need internet initially. A remote model selection changes where the extracted page text is processed.
If the result is empty or clearly about the wrong page, check the active tab, Use page, and whether the page has loaded. Then try a specific section. Start with a shorter source if the local model cannot handle the full page usefully.
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.
Download OGAD, connect the extension, and turn one long page into a summary with facts you have checked.