Library / SDK
VolcanicArts/VRCOSC avatar
VolcanicArts/VRCOSC

VRCOSC: monthly Beta releases, a community blacklist for the ChatBox, and modules that live in another repository

A modular node-programming language, program creator, animation system, toolkit, router, and debugger made for VRChat

580 stars50 forksC#GPL-3.0

At a glance

What is it?
VolcanicArts' wrapper around VRChat's OSC system, and the parts that are less obvious than the feature list: where the first-party module code lives, what the ChatBox blacklist actually is, and what Pulse removes from the build.
Who is it for?
VRCOSC makes sense for someone already writing OSC for VRChat who wants the parameter plumbing, the ChatBox and a place to find other people's programs in one application, and for someone who would rather write a graph in Pulse than contribute a C# module. Two things to weigh first.
Can I use it commercially?
Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
Is it still maintained?
Yes. The repository last received commits 17 days ago.
What is it written in?
Mainly C#, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • VolcanicArts/VRCOSC580 ★ · +12
Star history
Repository2026-09-212026-11-15
VolcanicArts/VRCOSC568580

12 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Calendar-versioned releases land monthly and the newest is tagged Beta

The release names encode the date rather than a sequence. The three most recent are 2026.708.0 on 2026-07-08, 2026.807.0 on 2026-08-07 and 2026.906.0 on 2026-09-06, and the last of those carries Beta in its title. So the pattern is a build per month, with the build counter available for a second attempt inside the same month, and the current head of the line is explicitly pre-release. That matters more here than it would for a library, because the application updates itself: automatic updates are one of the listed features, so the version you get is decided as much by the updater as by the release page. Anyone pinning behaviour for a live avatar should treat the monthly build as the unit of change and read the Beta marker as a signal to test before relying on it.

The documented way in is a Windows setup executable and a run button

There is no package to add and no plugin directory to point at. Getting started is three steps: download and run VRCOSCSetup.exe from the latest releases page, enable whichever modules you want, and press the run button. Everything else is routed through the documentation site, with an FAQ for install and prefab problems and a Discord server for the rest. Optional first-party prefabs are downloaded separately from the downloads page and dragged onto an avatar from there. The repository tree reinforces the Windows shape of the thing: a solution file, a .sln.DotSettings file, a global.json that pins the .NET SDK, and a Directory.Build.props for shared MSBuild properties, alongside two project directories, VRCOSC.App and VRCOSC. Nothing on the page addresses any platform other than the one the setup executable implies.

The first-party module code lives in a second repository

VRCOSC is the host, not the catalogue. The page states that the official modules' source code is in a separate VRCOSC-Modules repository, and the design goal is explained directly: users should not have to hunt for a separate download for each OSC program, so one application is the single source. What makes that work across independently written modules is a contract rather than a shared codebase. All modules support sending generic parameters that are standardised, and the point of standardising them is that a public avatar can consume them, which is why a module someone else wrote can drive an avatar you downloaded from someone else entirely. Most modules also carry ChatBox support and expose generic variables for it, so the same message surface is available without each author inventing one.

The ChatBox world blacklist is a community file with a social contract attached

One feature has a dependency outside the project and a request attached to it. The ChatBox uses a community-created list, a JSON file held in a separate repository, to block the ChatBox from being used in certain worlds. The list is fetched rather than compiled in, so the set of blocked worlds can change without a VRCOSC release, and a user who has never opened the app sees a behaviour they did not configure. The setting can be turned off in the app settings. The page nevertheless asks users to keep it on out of respect, which is worth naming plainly because it is the one place where the documentation asks for compliance rather than describing a setting, and because it tells you the maintainers consider the block list a social arrangement rather than a bug workaround.

Pulse exists so you do not have to write a module

Pulse is a node-programming language inside the application, and its stated purpose is narrower than the feature list makes it sound: it lets users make custom behaviour without making a module. That is the design decision to understand. A module is compiled C# shipped through the SDK, which means a build step, a version to track and a distribution problem on another person's PC. A node graph is data inside the running application, so it can be edited, saved per avatar and shared the way any other configuration is. The documented capabilities cover connecting APIs to VRChat, routing the speech engine into parameters and doing arithmetic, and the module table shows the boundary being used in practice, since the Twitch module connects Twitch events into Pulse rather than reimplementing that wiring in C#.

Body signals and a shock device end up driving avatar parameters

The official module table is where the concrete list lives, and it is worth reading as a catalogue of inputs. Media handles Spotify and YouTube display in the ChatBox along with control over media sessions. Twitch wires live events into Pulse. Pulsoid and HypeRate each connect to an external heart-rate service and expose the reading, with both linking to supported device lists. Speech To Text listens to speech and puts the result in the ChatBox, and Voice Commands drives avatar parameters from the same source. PiShock controls groups of shockers from the avatar or from the voice, which is the module to think hardest about before enabling. Alongside them sit ParameterSync for carrying parameters between avatars, Maths for defining equations that drive parameters, Counter for counting parameter changes so they can be displayed, Client Events for reacting to VRChat events, Keybinds, DateTime, Hardware Stats and two SteamVR modules for session statistics and haptics.

Per-avatar profiles and automatic updates sit beside the monthly build

The remaining infrastructure features are what turn a set of tools into a product. Per-avatar profiles keep configuration attached to the avatar rather than to the machine, which matters in a platform where you can walk into any world with any avatar. A built-in router means the modules do not each need their own OSC listener, and common API interfaces are the other half of that arrangement, giving other frameworks a way into an OSC project rather than making every integration bespoke. Drag-and-drop Unity prefabs are how the avatar side gets configured, and debug tools close the loop for anyone writing a module. Automatic updates then connect all of it to the release cadence, which is why the monthly build number and the Beta marker are more than a version string: they are the shape of the update you will receive.

Editorial conclusion

VRCOSC makes sense for someone already writing OSC for VRChat who wants the parameter plumbing, the ChatBox and a place to find other people's programs in one application, and for someone who would rather write a graph in Pulse than contribute a C# module. Two things to weigh first. The world blacklist that mutes the ChatBox is a JSON file maintained in someone else's repository, so the behaviour of your install can change without a VRCOSC release, and the project asks you to leave it enabled. And the documented route in is a Windows setup executable with automatic updates behind it, so if your environment is not Windows you are reading the page for the SDK and the module contract rather than for an install path. Read the SDK getting-started page before writing anything: the interface for third-party modules is the part of this project other tools depend on.

Frequently asked questions

what is vrcosc

VRCOSC is a wrapper around VRChat's OSC system built as a desktop application. It provides a custom node-programming language called Pulse, a ChatBox animation system, per-avatar profiles, a built-in router, automatic updates, shared API interfaces, drag-and-drop Unity prefabs and debug tools, so that users download one program rather than hunting for separate OSC tools.

how to install vrcosc

Download and run VRCOSCSetup.exe from the latest releases page, enable the modules you want to use, then press the run button. First-party prefabs are downloaded separately from the downloads page and added to an avatar from there.

Does VRCOSC run outside Windows?

The page documents only VRCOSCSetup.exe, and the repository ships a Visual Studio solution, a .sln.DotSettings file, a global.json SDK pin and Directory.Build.props. No other platform is mentioned, so the installation route described is the Windows one.

Can I turn off the ChatBox world blacklist in VRCOSC?

Yes, the setting can be turned off in the app settings. The list is a community-created JSON file kept in another repository, and the documentation asks users to leave the blocking on out of respect.

Where do I find the source code for the official VRCOSC modules?

In a separate repository, VRCOSC-Modules, rather than in the VRCOSC repository itself. All modules send generic parameters that are standardised so public avatars can use them, and most expose generic ChatBox variables. The SDK getting-started page covers writing your own.

Official sources

  1. Issues
  2. License: GPL-3.0
  3. README
  4. Releases
  5. VolcanicArts/VRCOSC on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/volcanicarts-vrcosc.svg)](https://hysenlabs.com/projects/volcanicarts-vrcosc)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/volcanicarts-vrcosc.svg)](https://hysenlabs.com/projects/volcanicarts-vrcosc)

Was this useful?