Install and pair Wren Companion

Wren Companion lets browser dapps request accounts, permissions, networks, and signatures from the Wren desktop wallet running on the same computer.

Companion is not a wallet or signer. It does not need your recovery phrase, private key, keystore password, or hardware-wallet PIN.

Before you begin

Install Wren 0.1.11, or a later compatible desktop release, and keep the desktop application running.
Use a current Chrome, Brave, or Firefox browser.
Use a disposable browser profile and a test-only wallet account for the first connection.
Remove or disable another extension that claims to be Wren; do not pair an archive from an unofficial location.

Companion 0.1.3 needs Wren 0.1.11 or a later compatible build. Update the extension separately from the desktop. Both browser stores currently list 0.1.2, which remains compatible with Wren 0.1.11. Use a verified release archive for the 0.1.3 retry fixes.

Install from the Chrome Web Store

Open Wren Companion in the Chrome Web Store.
Install the extension in Chrome or Brave and confirm the browser prompt.
Pin Wren Companion to the browser toolbar if you want its status to remain easy to reach.

Continue with Compare the pairing code.

Install from Firefox Add-ons

Open Wren Companion on Firefox Add-ons.
Select Add to Firefox and confirm the browser prompt.
Open Wren Companion from the browser toolbar or extensions menu.

Continue with Compare the pairing code.

Use a release archive

Use a verified release archive for Companion 0.1.3 while the browser stores list an earlier version.

Open the Wren Companion v0.1.3 release. Download the package for your browser and the verification files:

wren-companion-0.1.3-chrome.zip for Chrome or Brave, or wren-companion-0.1.3-firefox.zip for Firefox;
wren-companion-0.1.3-compatibility.json;
SHA256SUMS from the same release.

Calculate the archive hash:

sha256sum wren-companion-0.1.3-chrome.zip

On Windows, calculate the same hash in PowerShell:

(Get-FileHash -Algorithm SHA256 '.\wren-companion-0.1.3-chrome.zip').Hash.ToLowerInvariant()

Use the Firefox filename instead when installing for Firefox. The calculated hash must exactly match the archive’s entry in SHA256SUMS. Also verify the GitHub artifact attestation.

Check that the compatibility file names Companion 0.1.3 and the archive that you downloaded. It must use protocol 3 and name the official Wren repository, main branch, and minimum desktop commit. Wren 0.1.11 satisfies that minimum. Your installed desktop commit must be the listed commit or a later commit on that branch.

Stop if the archive, checksum, compatibility metadata, repository, or attested source does not match.

Extract the ZIP into its own directory. Chrome and Firefox packages have different background manifests and are not interchangeable.

Load the Chrome archive locally

Open chrome://extensions in Chrome or brave://extensions in Brave.
Enable Developer mode.
Select Load unpacked.
Choose the directory where you extracted the Chrome archive.
Pin Wren Companion to the browser toolbar if you want its status to remain easy to reach.

Load the Firefox archive temporarily

Open about:debugging#/runtime/this-firefox.
Select Load Temporary Add-on.
Choose manifest.json inside the extracted Firefox archive.

Compare the pairing code

Start Wren desktop if it is not already running.
Open Wren Companion from the browser toolbar.
Wait for Companion to display Pair this Companion and a six-digit code.
Wren desktop displays a connection request with its own six-digit code and the extension origin.
Compare all six digits. If they differ, select Decline, remove the extension, and verify its source again.
If they match and you initiated this installation, select Accept in Wren.

After approval, Companion pins the identity of this Wren installation. Normal reconnects to that exact desktop identity do not require another code comparison.

Connect a browser dapp

Open a dapp using your disposable browser profile.
Select Wren from the wallet choices. Dapps that support EIP-6963 should discover it by name.
Review the connection request in Wren desktop.
Confirm the requesting site, permitted account, and network before approving.

Each dapp receives only the accounts and networks you permit. When a dapp does not specify a network, Companion lets you choose one; check that network in Wren before approving the request.

Resolve common pairing states

Wren is unavailable

Start Wren desktop, confirm it is listening locally, then reopen Companion.

Update Wren

The installed Companion requires a newer compatible desktop build. Do not bypass the warning. Verify and install a supported Wren release, then select Reconnect.

Wren identity changed

Companion no longer recognizes the desktop installation. Reset pairing only if you expected Wren’s profile or installation identity to change. A reset creates a new Companion installation key and requires another code comparison.

Pairing failed

Keep Wren running and retry once. If it fails again, verify that desktop and Companion versions satisfy the published compatibility metadata before resetting either side.

Revoke or reset pairing

To remove Companion’s access from Wren, open Control center → Settings → Connections, find the paired browser under Browser companions, and select Revoke.

To replace Companion’s local pairing identity, open Companion and select Reset pairing twice to confirm. Compare the new six-digit code before accepting the new request in Wren.

Removing the extension also removes its browser-local pairing key. It does not remove accounts or signers from Wren desktop.

For the precise boundary, read the Companion security policy and privacy policy.