Getting Started

VRCS runs alongside VRChat and gives you monitoring, moderation, and history tools. Access is tied to your Nyxall account, so setup starts on this website and finishes in the app.

What you need

• A Windows (x64) or Linux (x64) machine. Windows gets the full experience, including the VR overlay; on Linux, Steam/Proton integration, VRChat log reading, Open in Game and headset overlays have not been tested yet (see Installation).
• A VRChat account.
• A Nyxall account with access to VRCS. Creating an account is free; access is requested and approved separately (step 1 and 2 below).

You don’t need an access key. The app no longer asks for one: your Nyxall account and its approved access are what unlock it.

1. Create your Nyxall account

Create an account with a handle, your email address and a password, then enter the code we email you. An account on its own doesn’t include any members-only builds.

2. Request access and wait for approval

Signed in, request access to VRCS. The studio reviews each request by hand, so this can take a while. Once it’s approved, the build appears on your downloads page — requesting again won’t speed it up.

3. Download and install

Download the installer for your platform from your downloads page. The installation guide covers each OS, including how to check the file’s SHA-256 checksum and what to do about the Windows SmartScreen prompt.

4. Sign in with Nyxall

On first launch the app asks you to connect your Nyxall account. Choose Sign in with Nyxall: your browser opens the Nyxall sign-in page, and after you approve, the app confirms your access and unlocks. The app never sees your Nyxall password.

If the app says your account has no access, your request hasn’t been approved yet — or you signed in with a different account than the one you requested access from.

5. Log in to VRChat

Sign in with your VRChat credentials inside the app. Credentials go directly to VRChat — the app stores a session on your machine, the same way the official client does. Two-factor codes work as expected.

6. Let it run

The app is designed to stay open in the background (or system tray). While running it keeps your local history — instances, players, and events — re-checks your access, and checks for updates automatically. See Updating for how updates behave.

Next steps

• Skim the feature overview on the project page.
• If something misbehaves, the troubleshooting guide covers the common cases.