Explicit opt-in

Try what's next. Keep Stable separate.

Experimental is for testing new capabilities, not production-critical work. Choose a separate MSI installation or a portable ZIP. Its signed release feed, application data and installer identity stay separate from Stable.

EXPERIMENTAL - explicit opt-in

Choose your Experimental package.

Checking for a signed Experimental release...

For everyday use, keep Stable downloads. Installed Stable automatic updates never subscribe you to Experimental.

Experimental MSI installer

A separate Windows installation, with its own application data and Start-menu entry. Does not upgrade or remove Stable. Preview updates are installed manually.

Checking installer availability...

Experimental portable ZIP

No installation required. Extract the complete package into a new writable folder. Keep its portable marker and runtime files; application data stays alongside them.

Downloads appear only after verification against the desktop's pinned RSA-PSS release key.

Before launching

Keep your test environment separate.

Close any running BobCommander desktop first: Stable and Experimental share the Windows user/session single-instance guard.

The MSI uses the fixed Program Files\BobCommander Experimental directory and its own Start-menu entry. Settings, logs and the queue use %LOCALAPPDATA%\BobCommander Experimental; Stable data is not migrated. Install future Experimental releases manually.

  1. Extract the entire ZIP into a new folder. Keep portable.mode, the Mcp folder and all runtime files. Do not extract over Stable or an older Experimental build.
  2. Portable settings, logs and the durable queue stay beside the extracted application. Do not copy Stable's settings or queue into this folder or switch portable mode off. This separates application data, not access to your real files.
  3. Use disposable copies of files and keep backups. Approving a plan can change real data; completed operations are not automatically rolled back.
  4. Start this folder's desktop for MCP plans and point the client at this folder's bobcommander.exe. Close it before reopening Stable. Portable builds do not auto-update.
Integrity and limits

Experimental is not a security exception.

Signing, integrity checks, tests and reviews still apply. Release-channel separation does not remove a blocked CI or security gate. A guide or local test package is not proof of public availability.

Experimental manifest · Detached signature · Checksums · Release notes

Verified ZIP SHA-256: Not available

Verified MSI SHA-256: Not available

The existing manifest channel is called Prerelease on the wire and EXPERIMENTAL here. Product versions retain major.minor.build. A build becomes Stable only after a separate release decision; users are never migrated automatically.

Report reproducible problems without attaching secrets or private file contents through GitHub issues.