Connect a client
Browser clients
Open the companion for QR exchange and remote connections. For browser signing, download and load the extension, then reload your client tab. The extension opens its own companion tab.
The nSealr extension provides the standard NIP-07 signing interface. A client can ask for your public key, request a signature, or request supported encryption. The companion handles QR exchange; you approve key operations on the device.
| Client | Browser login | Remote signer login |
|---|---|---|
| Coracle | Use Browser Extension | Use Remote Signer |
| noStrudel | Browser Extension | Nostr Connect |
Choose the matching login option, approve the displayed website origin in the companion, and complete the device QR exchange. Compare the full npub before posting. Reconnect the client after changing the selected identity.
Grant access only to the client you intend to use. The connected client can still read the content you write there. Keeping the key offline does not make a compromised computer safe for private text.
Remote connections
NIP-46 lets a client connect to a remote signer. The companion handles this connection and forwards key operations to the QR device. Connection keys are separate from your Nostr identity key.
In the companion, choose a secure relay and Open session. Paste its pairing link into the client’s remote signer login. Check the client public key shown by the companion before allowing it. Keep the companion open; reloading or closing it ends that session and requires fresh pairing.
A connected session does not approve future signatures. Each operation still needs the device’s decision. Unsupported requests return an error.
Private messages
The companion can send one-to-one NIP17 messages and open a selected message. Use an identity created from recovery words or an nsec. A 2-of-3 group supports signing and public-key requests, without NIP-44 encryption or decryption.
Set your inbox relays, then enter the recipient’s npub and write your message. Both identities need signed inbox preferences so the companion can find where to send the recipient’s copy and your copy.
Review each requested operation on the device. The companion shows which relays accepted each encrypted copy. Retry sends only copies that remain unaccepted. Relay acceptance does not mean the recipient has read the message.
Opening a message needs two device exchanges to open and verify its layers. Clear local messages when you finish reading. The computer receives approved plaintext; only the identity key remains on the device.
Integration
Use existing NIP-07 or NIP-46 support in your client. Start with getPublicKey
and signEvent; verify the returned event and display a clear cancelled state.
See the companion source
for the current build and connection steps.
Client qualification notes record the checked client versions, journeys and their limits. The protocol interfaces are defined in NIP-07 and NIP-46.