ALCOMD3

Languages: English | 日本語 | 繁體中文 | 简体中文

ALCOMD3 is an independent desktop tool for VRChat project and VPM package management. It provides project workflows, VPM repository and package management, backups, updates, and optional local MCP integration.

This project originated from vrc-get/ALCOM, but ALCOMD3 is maintained as its own project. It is not an official product of VRChat or VCC.

Features

  • VRChat project management, project copying, backup, and restore workflows.
  • VPM repository and package management.
  • Material Design 3-style desktop interface with theme customization.
  • Windows x64, macOS Apple Silicon, and Linux x64 releases and updates published from this repository.
  • The normal startup check downloads signed updates without confirmation by default and installs them before the next launch; this can be disabled in Settings.
  • vcc:// URL association for VCC-compatible shortcuts.
  • Optional local MCP bridge for AI-agent access to ALCOMD3 project, repository, package, environment, activity log, and technical log data.

For MCP setup and tool details, see docs/mcp.md.

Downloads

Prebuilt releases are available from the official website and GitHub:

https://alcomd3.cqmhv.com/ https://github.com/CQMHV/ALCOMD3/releases

The first formal multi-platform build is the 2.1.2-beta.1 beta. Its asset names identify the platform and architecture: Windows uses ALCOMD3_{version}_windows_x86_64_setup.exe.zip, macOS Apple Silicon uses ALCOMD3_{version}_macos_aarch64.dmg, and Linux x64 provides ALCOMD3_{version}_linux_x86_64.AppImage plus ALCOMD3_{version}_linux_amd64.deb. The AppImage supports in-app updates; the DEB intentionally leaves updates to the package manager.

The website presents stable and beta downloads as separate choices without designating a recommended channel. When the browser platform is recognized, only the matching stable package card is visually emphasized; beta packages are never emphasized. Stable 2.1.1 remains available through its GitHub Release page; its legacy asset names are not converted into direct website download links.

Release notes are available from each GitHub Release and under release-notes/.

Development

Requirements:

  • Rust stable toolchain
  • Node.js and npm
  • Windows build tools when building the Windows MSVC target

Start the Tauri development app with the Vite development server:

cd vrc-get-gui
npm run tauri dev

For frontend-only development:

cd vrc-get-gui
npm run dev

Build and release procedures are documented in docs/RELEASE.md. The main documentation index is docs/README.md.

Repository Layout

  • vrc-get-gui/: ALCOMD3 desktop GUI and frontend.
  • vrc-get-gui/windows-installer-wrapper/: helper executable used by the Windows installer.
  • alcomd3.config.json: shared ALCOMD3 product and release configuration used by xtask and the website; external packaging templates are checked against it by tests.
  • alcomd3-mcp/: stdio MCP bridge executable.
  • alcomd3-mcp-protocol/: shared local IPC protocol types and constants used by the GUI and MCP bridge.
  • alcomd3-app-paths/: shared local data directory and MCP endpoint path helpers used by ALCOMD3 processes.
  • vrc-get-vpm/: VPM-related library code.
  • vrc-get/: command-line compatibility code.
  • xtask/: build, bundle, release, and maintenance helper tasks.
  • website/: ALCOMD3 website.
  • docs/: project documentation.
  • release-notes/: release notes kept with the repository.

Some directory and crate names still include vrc-get for compatibility with existing code and packaging boundaries.

Documentation

Licenses

The main project code is licensed under the GNU Affero General Public License v3.0 or later (AGPL-3.0-or-later). See LICENSE and LICENSE-NOTES.md.

The application includes an in-app Licenses page for dependency and third-party resource notices. Additional third-party asset notes are maintained in vrc-get-gui/THIRD-PARTY.md.

Contributing

Issues and pull requests should focus on ALCOMD3 behavior, documentation, releases, compatibility, and tooling.