Skip to content

PUBLIC INFORMATION

Rust+ pairing extension

Use the same secure WipeWire pairing helper in desktop Chrome or Microsoft Edge.

Checking this browser…

WipeWire is looking for the pairing extension.

Chrome Web Store · listing pendingMicrosoft Edge Add-ons · listing pending

Current availability

WipeWire is still in private testing. Signed-in testers can now download the reviewed v0.3.0 package and follow the manual Chrome or Edge install steps. Ordinary one-click installation will become available after each browser store completes its separate review.

Sign in to get the tester package →

Connect without copying a code

Select Connect Rust+ in WipeWire, sign in through the official Steam and Facepunch pages, and the extension completes the handoff automatically. You return to WipeWire ready to pair your server. Your Steam password and Steam Guard code stay on Steam.

Chrome and Edge use one reviewed build

Both browsers use Chromium Manifest V3, so WipeWire keeps one extension codebase and produces matching Chrome and Edge packages. Each store assigns its own listing and extension ID; the website checks both without receiving browsing history or page content.

Pair a server

  1. Install the signed-in tester package in desktop Chrome or Edge, then refresh WipeWire.
  2. Open guided setup, confirm the team shown, and select Connect Rust+.
  3. Sign in through the official Steam and Facepunch pages. The extension sends the authorization result automatically and returns you to WipeWire.
  4. Join your server in Rust, press ESC, and choose Rust+ → Pair with Server or Resend.
  5. WipeWire confirms when the server arrives. You can then pair smart devices in-game.

You do not need to copy a code during normal setup. Manual linking is available under troubleshooting if the automatic connection fails.

Small permission surface

The extension stores temporary pairing progress, receives authorization only on Facepunch’s companion page, and sends the token only to the WipeWire gateway. On the exact WipeWire website origins it exposes its version, public extension ID, and supported pairing protocol so the site can detect it. The short-lived pairing session passes directly to the extension through browser messaging, never through page-wide events. It does not request browsing history, cookies, clipboard access, all-sites access, or remote executable code.