MultiClaw Chrome Extension not detected

Last updated Mar 30, 2026

If you see "Companion not detected" or the recording button is greyed out, start with two quick checks: is the MultiClaw Chrome Extension installed in Chrome, and is it toggled on? Those two issues account for most cases.

Extension not installed

Open the Chrome Web Store and search for MultiClaw Chrome Extension, then click Add to Chrome. Once it installs, reload your browser tab and try again.

Extension installed but disabled

Open Chrome and go to Extensions (the puzzle-piece icon in the toolbar, or navigate to chrome://extensions). Find the MultiClaw Chrome Extension entry and make sure the toggle is turned on.

Native messaging host not registered

This happens most often after reinstalling the Desktop app. Quit MultiClaw Desktop completely, then reopen it — the app re-registers the native messaging host on startup. After it reopens, refresh the browser tab.

Extension installed in the wrong Chrome profile

The extension must be installed in the Chrome profile you are currently using. Click your profile avatar in the top-right corner of Chrome to see which profile is active. Either switch to the profile that has the extension installed, or reinstall the extension in the current profile.

Browser not supported

The MultiClaw Chrome Extension uses native messaging, which only works in Chrome, Chromium, Edge, Brave, and Arc. Safari and Firefox are not supported. Switch to a supported browser to use browser automation.

Desktop app not running

The extension requires MultiClaw Desktop to be open. If the Desktop app is closed, the extension has nothing to connect to. Open MultiClaw Desktop first, then reload the browser tab.

macOS permission issue

On macOS, if you moved the MultiClaw Desktop app out of /Applications after installing it, macOS may block the native messaging host. Move the app back to /Applications, then reopen it.

Tip:

If none of the steps above work, quit both the Desktop app and Chrome completely, reopen the Desktop app first, then reopen Chrome. A full restart of both clears most stubborn detection failures.