You already have the right website open and signed in. OGAD (Off Grid AI Desktop) Pro can run a browser task in that browser through the Off Grid AI extension. You can use a local model to collect information from the session you already use, then check the answer before you act.
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.
What changes from the built-in browser?
The built-in browser has its own session. A website open in Chrome is not automatically signed in there. The extension gives Web Use a route to your normal browser, where your existing login and open pages can be used.
Start with a reading task. For example, collect the status and last update from three support tickets. The result is a small table you can check, with links back to the tickets. Local inference keeps the model work on your computer. The support website still receives normal browser requests.
This is a Pro Web Use workflow. Prepare a local tool-capable text model, any local specialist required by your selected strategy, and the browser extension. A text chat that works in the panel does not by itself prove that browser tasks are connected.
Install and connect the browser extension
The extension needs Node.js 20 or later for a source build. It is not listed in the browser stores in this setup. Downloading 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.
Choose this browser for Web Use
- Open the paired extension's Settings > Tasks.
- Under Web Use, choose Default browser in the Browser control. This means the browser running the extension.
- Enable browser tasks under This browser when offered.
- Choose a local model strategy. Same as Chat uses the selected chat model for that strategy; check any separate specialist selections too.
- In OGAD, turn Assistant on and give it one small Web Use task.
Try this with pages you are allowed to read:
Use Web Use in my default browser to read these three ticket URLs: [links]. Return ticket title, current status, last stated update date, and source URL. Mark a missing field as not found. Do not change tickets or send replies.
Follow the run in Tasks. On Chrome, a browser message can show that the extension is debugging a task tab. This is how the task drives real page controls. Use its cancel control or OGAD's stop control if you need to stop the run.
Check a first useful result
Open the source for the first row. Compare the status and date with the page. An update date is not necessarily the date the ticket was resolved. Keep those meanings separate in your brief.
If one page requires another login step, complete it yourself when appropriate. If a challenge or page error blocks reading, ask the assistant to retain the rows it checked and name the missing row. Do not turn a blocked source into a guessed answer.
Once the first task works, use the same columns for a larger set. Keep the source links with the output. They make the table useful for later review and help you find changes when the website updates.
Where can the task stop working?
| Symptom | First check |
|---|---|
| A fresh browser session opens | Web Use is still set to the built-in browser |
| Panel chat works but tasks do not | Pairing, the browser-task switch, and Pro readiness |
| Task cannot find a page control | Page loading, login state, and the selected model strategy |
| No local reply | OGAD is running and the selected model is ready |
| A site asks for confirmation | Read the request and decide whether it belongs in your task |
A signed-in session can expose private work. Choose the pages needed for the task. Instructions embedded in a web page are source content; they are not permission to change your brief. Review any action that would submit information or change an account.
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 and connect the extension. Start with three pages, four fields, and a result you can check in a few minutes.
Top comments (0)