Vibe Code Pro · Windows x64

VCP beta downloads

A coding assistant for your local workspace, with explicit permissions and retained task history. Start with a small workspace and a reviewed task.

Native 0.2.0-beta.1 · VSIX 0.2.1Candidate date

Start here

Windows installer

Per-user setup with a stable launcher and a separate directory for your data.

Windows x64 · EXE · 76.6 MiB

Download Windows installer
SHA-256 & file details
File
vcp-0.2.0-beta.1-windows-x64-unsigned-setup.exe
Size
80355103 bytes
SHA-256
7d6fdc48bc6b273e30b3738dd45664d80484eebe2bb94d6169a09c37547b44ae

The matching downloads

Use the files from this release together. The VS Code extension connects to the native engine; it does not install it.

Portable ZIP

Extract to a new directory and launch the native executable directly. Keep data outside the extracted payload.

Native 0.2.0-beta.1 · 73.8 MiB

Download portable ZIP
SHA-256 & file details
File
vcp-0.2.0-beta.1-windows-x64-unsigned.zip
Size
77348203 bytes
SHA-256
915c0d36428709e01c5a0e13f393a15fbbdd0986c93624646ddeef408ddca53d

VS Code extension

Install the VSIX in VS Code, then select your installed engine and data directory explicitly in User settings.

VSIX 0.2.1 · 174.9 KiB

Download VS Code extension
SHA-256 & file details
File
vcp-local-0.2.1-win32-x64.vsix
Size
179074 bytes
SHA-256
d7d58e969bf6857b607d9e70e65349dd32645f90c1434292d10627073ce4e10b

Before your first task

  • Native Windows x64 · local NTFS paths
  • PowerShell 7 · standard Program Files location
  • VS Code 1.138.0 · for the extension
  1. Install and confirm the selected engine.

    Choose separate program and private data directories. Follow the installation guide.

  2. Set your policy and budget.

    Provider setup and live tasks require your credential and explicit spending caps. Never put secrets in settings or shared logs. Follow the onboarding guide.

  3. Connect VS Code deliberately.

    Select the resolved native executable and data directory in User settings. Reconnect observes history; it does not resume work. Set up the extension.

Verify your download

Compare each file’s SHA-256 with the checksum record. Matching hashes identify the bytes; they do not authenticate an unsigned publisher.

Artifact pair
1dba45922e0c34a04880f2ed4c5a07a65882b809559104aee70506b88838bcc7
Source commit
f81b2c5062dad1f8d13d72ffb5fb8006eeea9229