You start a question beside a web page, then need more space for the next part of the work. Pair the Off Grid AI extension with OGAD (Off Grid AI Desktop) to share browser conversations with the desktop. You can continue the discussion without copying each message into a new chat.
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.
The desktop gateway supplies model access. Pairing adds the approved link used for shared conversations and desktop tools. A working browser reply alone does not show that conversation sharing is enabled.
This distinction matters when you first try the extension. An unpaired browser chat can remain in extension storage. The paired desktop link exchanges conversation records so the desktop can show the related history.
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.
Use a harmless public page for this first check. Give the chat a distinctive topic so you can identify it among other conversations. Compare the actual messages, not only the chat title.
The useful result is the conversation you were working on, with its existing context. If the desktop does not show it, check the paired state before recreating the chat. A copied first question in a new conversation is not the same continuity workflow.
Suppose you used the browser to understand a setup guide. On desktop, ask:
Use the requirements we already checked to make a preparation checklist. Separate the items I have from the items I still need. Ask me about any item you cannot determine from this conversation.
Provide the missing facts about your computer. The conversation contains what you discussed; it does not automatically know your full setup.
Keep page addresses in the chat. The desktop conversation is not a permanent live copy of the browser tab. If the source page changes or was only partly extracted, check it again before treating earlier notes as current.
You can then draft a short note from the checked conversation. Ask for one result, such as a list of unresolved requirements. Keeping the next question narrow reduces the chance that the model fills gaps with assumptions.
A shared conversation and a selected model are separate state. Confirm the active route when you move to desktop. Choose a downloaded local model if you want the continuation processed on that computer.
A browser conversation can contain private page text. Sharing it with your paired desktop makes that text available there. Protect both applications' stored history and choose the source material deliberately.
| What you see | What to check |
|---|---|
| Browser reply works, desktop history is empty | Pairing and desktop link state |
| A similar title has different messages | The actual conversation content and origin |
| Chat stops updating | Desktop availability and the extension connection |
| Reply uses an unexpected route | Active local or remote model selection |
Keep OGAD running while checking sharing. If you reconnect after a failure, inspect the existing conversation before starting another one. Do not assume that a connection error deleted the browser history.
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, pair the extension, and confirm one browser conversation appears on desktop before moving an important project across.