Harness beside your browser work
Connect the page.
Keep the conversation.
Keep the same conversation beside your browser. Follow the active page in PiP, keep a page fixed, or select a section and ask in place. Work from Dot, research, and everyday browser tasks can all start here.
For desktop Chrome 125 or newer. Updates arrive through the store.
Keep your Harness work tab open during setup. Installation does not require starting another conversation or moving your draft.
Add it from the Chrome Web Store
Choose Add to Chrome on the Harness listing, then confirm in Chrome.
Connect your account
The extension opens its setup page. It looks for your existing Harness tab and signed-in account. Choose Open Harness ↗ if already connected, or use the sign-in option. If you need an account, choose Create a Harness account ↗ in setup or create one or sign in on the Harness website, finish the email sign-in in this browser, then return to extension setup.
If setup does not open, find Harness on
chrome://extensionsand choose Details → Extension options.Choose access, then try it
Follow Account → Access → Try it in extension setup. Choose the sites Harness can access in Chrome; access to all sites is optional. Enable Follow the active page to include your current permitted page when you ask in PiP. Browser automation has a separate setting. Then visit a normal webpage, hold your chosen selection key (Alt by default), and click a section. The toolbar icon can start selection too.
If your companion is open, the selected section joins its active conversation. Otherwise, ask in the prompt on the page and use Float ↗ to continue in the companion.
Your context, with clear boundaries
PiP shows the page it will use. Choose Keep this page to hold context fixed, or Pause page context to stop using browser pages in that conversation. A running action stays attached to its original page when you change tabs. Page context and selected screen sharing are separate. A screenshot is optional. Browser automation has its own setting, and Chrome shows its debugging banner during native browser control. Chrome’s internal pages and some protected sites cannot be read.
Screen indexing and local history stay on your device. Selected evidence and conversation context may travel through Harness and your selected model provider when answering. See the privacy details for each mode.
Getting back to work
Return to the Harness tab you left open to continue. If connection fails, use Retry in extension setup and check Chrome’s site access for Harness.
Open your workspace ↗