VRC Launcher

A Rust + Tauri alternative and variant of the official VRChat Quick Launcher

Native launcher flow for VRChat installs, profiles, instance startup, and window tiling.

About • What It Does • Launch Multiple Clients • Development • License Direction

---

VRC-QL-TS is a desktop launcher for VRChat-oriented multi-instance and profile workflows, built with a Vue frontend and a Rust/Tauri backend. It is designed as an alternative and variant of the official VRChat Quick Launcher, with the goal of providing a lighter native desktop app for picking installs, managing profiles, launching instances, and arranging running VRChat windows.

About

This project is a Tauri/Rust implementation of an alternative take on the official VRChat Quick Launcher.

It is intended for people who want a denser version of the VRChat Quick Launcher, with clearer organization for installs and profiles so it is easier to know what is what at a glance.

At a high level, the app is meant to help with:

• organizing VRChat installs
• managing launcher profiles
• starting VRChat instances with a simpler desktop flow
• launching multiple clients in a controlled queue
• arranging visible VRChat windows on screen

What It Does

The current codebase is focused on the initial launcher foundation:

• Vue app bootstrapping and theme/config loading
• Launcher, installs, profiles, and settings pages
• Native Tauri command for launching VRChat instances
• Native Tauri command for tiling visible VRChat windows on Windows

Launch Multiple Clients

The launcher includes a queue-based flow for starting multiple VRChat clients in one pass.

• add one or more profiles to the launch queue
• reorder the queue to control launch order
• enable or disable individual entries without removing them
• assign installs per queue entry
• reuse the same profile multiple times with different install settings
• launch the queue from top to bottom

When launching a batch, the app waits for VRChat to open between profiles before continuing to the next entry. If auto-layout is enabled and more than one profile is launched, the app can also tile visible VRChat windows afterward.

Profile Slots

The profile slot field maps to the VRChat launch argument --profile=N.

• 0 is the normal default or Steam-style launch path, so the launcher does not add --profile=0
• 1 is the first separate profile slot
• 2 is the second separate profile slot
• higher numbers continue the same pattern

Use different profile slot values when you want launches to stay separated from each other in their local VRChat profile data. If two launch profiles use the same slot number, they are targeting the same VRChat profile slot.

Development

Technical summary: v0.1.0 • Vue 3 + Vite • Rust + Tauri 2 • Windows desktop

Requirements

• Node.js
• Rust toolchain
• Tauri 2 prerequisites for Windows
• Microsoft Edge WebView2 runtime on Windows for the desktop app to run

Scripts

npm run dev
npm run build
npm run typecheck

What The Scripts Do

Command	Purpose
npm run dev	Runs the Tauri desktop app in development mode
npm run build	Builds the production desktop bundle
npm run dev:vite	Runs only the Vite frontend dev server
npm run build:vite	Builds only the frontend assets
npm run typecheck	Runs vue-tsc --noEmit

Developer Notes

Repo Map

Using ARC-Client as the reference for how to document startup coverage, this is the minimal map of where this app starts and what each initial file is responsible for.

Path	Purpose
package.json	Frontend package metadata, app version, and dev/build/typecheck scripts
src/main.ts	Frontend entry point; loads config, applies theme, mounts Vue
src/App.vue	Main app shell; handles top-level navigation between pages
src/pages/	Primary desktop views such as Launcher, Installs, Profiles, and Settings
src-tauri/Cargo.toml	Rust package metadata and native dependency definitions
src-tauri/tauri.conf.json	Tauri product name, version, window config, bundle settings
src-tauri/src/main.rs	Native executable entry point
src-tauri/src/lib.rs	Tauri builder, plugin registration, and command wiring
src-tauri/src/commands/launch.rs	Launches VRChat or launch.exe, with optional process handoff wait
src-tauri/src/commands/window_tile.rs	Tiles visible VRChat windows across the primary display

Startup Flow

1. npm run dev starts the Tauri dev process.
2. Vite serves the Vue frontend.
3. Tauri loads the Rust backend from src-tauri.
4. src/main.ts loads saved config and applies the selected theme.
5. src/App.vue renders the shell and swaps between the core pages.
6. Frontend actions call Rust commands for native launch and window management behavior.

Notes On Platform Behavior

• The native launch flow is currently Windows-oriented.
• On Windows, the app runs through Tauri using Microsoft Edge WebView2 as its webview runtime.
• Window tiling is implemented for Windows and is a no-op on non-Windows platforms.
• The app window is currently configured as a standard resizable desktop window with a dark theme.

License Direction

This repository is licensed under the custom ComfyChloe Non-Commercial Copyleft License 1.2.

In practical terms, that means:

• people may view, share, and modify the code
• people may publish fixes, forks, and contributions
• distributed modified versions must remain under the same license
• distributed versions must include source code
• selling the code or redistributed builds is not allowed without separate written permission
• closed-source redistribution is not allowed

This is a custom license for this repository. It is not MIT, GPL, Apache, or MPL.