Optional local integration

Role Rover secure companion

Use Claude through your authenticated local CLI, or protect supported API credentials with your operating system's credential vault. Core Role Rover search and matching do not require this download.

Download version 1.0.3

Download only from getrolerover.com. The companion is separate from the Chrome Web Store extension and is optional.

Download the signed macOS installer

SHA-256: 65185879a091a1d3f85efd1ddce9ed0d264a63aa745131e4b6c26682d9ab7b09

This package is signed with Developer ID, notarized by Apple, and includes its stapled notarization ticket. Open it from Downloads and follow the standard macOS installer.

Download the Linux or manual macOS archive

SHA-256: e8a2b0298afc63804ec8a273a63ada8d6e399a35c358fa303add01f200977592

Download for Windows

SHA-256: aff0e14a379539ca57fb1c0db18c178d48623bb0be756c2ddc41578ddf1aa1b6

On macOS, verify the package with shasum -a 256 role-rover-companion-1.0.3.pkg. On Linux, use shasum -a 256 role-rover-companion-1.0.3.tar.gz. On Windows PowerShell, use Get-FileHash .\role-rover-companion-1.0.3.zip -Algorithm SHA256.

Install for your browser

The signed macOS installer automatically registers the published Role Rover extension for supported Chromium browsers. Manual and development installs still require Role Rover's 32-character extension ID from chrome://extensions.

macOS

  1. Open the downloaded PKG.
  2. Review and approve the standard macOS installer.
  3. Fully restart the browser.
  4. Return to Role Rover Settings and refresh the connection.

Linux or manual macOS repair

  1. Extract the tarball.
  2. Run ./install-role-rover.sh. It is already bound to the published Role Rover extension.
  3. Fully restart the browser.

The installer detects Chrome, Vivaldi, Brave, Edge, and Chromium. Development installations can still use ./native/install.sh EXTENSION_ID all as a manual fallback.

Windows

  1. Install Node.js if it is not already available.
  2. Extract the ZIP.
  3. Double-click install-role-rover.cmd. It is already bound to the published Role Rover extension.
  4. Fully restart the browser.

The installer registers the companion for the current Windows user and does not require administrator access. Development installations can still use the PowerShell script with an explicit extension ID.

Enable it in Role Rover

  1. Open Role Rover Settings.
  2. Enable Advanced Claude companion and approve Chrome's optional native-messaging permission.
  3. Choose Claude Max subscription or Anthropic API key.
  4. Review the disclosure and enable only the sharing appropriate for the operation.
  5. Refresh models and test the connection.

Claude Max mode requires the Claude CLI to be installed and authenticated separately. API-key mode stores the key in Apple Keychain, Windows Credential Locker, or Linux Secret Service.

What the companion can do

The companion accepts a narrow set of Role Rover operations: health and model discovery, bounded job analysis, consented monitor recommendations, verified-fact Application Pack selection, supported application-question assistance, and protected credential operations. It does not receive browser cookies, job-site passwords, CAPTCHA material, or application credentials.

Claude operations use Anthropic-hosted inference; they are not on-device inference. Role Rover shows the data boundary before consent and records attempted AI requests and responses locally in AI Activity. See the security overview and privacy policy.

Remove the companion

On macOS, open Terminal and run sudo "/Library/Application Support/Role Rover/uninstall-role-rover". macOS asks for an administrator password and then removes the host and every Role Rover browser registration.

On Linux, run ./native/uninstall.sh all from an extracted companion folder. On Windows, run powershell -ExecutionPolicy Bypass -File .\native\uninstall.ps1 all. A single browser name in place of all removes only that browser registration and retains the shared host.

After removal, disable the companion in Role Rover Settings. Core local matching continues to work.