Names and compatibility

Important

Commands in published builds The new vibe-viewer and vibe-sketcher launchers require a build that includes the renaming changes. Current published archives and available public source snapshots still use vibe-view and vibe-sketch. These deprecated commands remain supported with no removal date; vq is unchanged.

For examples elsewhere in this manual, substitute vibe-view for vibe-viewer and vibe-sketch for vibe-sketcher when using those published builds. A repository rename does not publish new source or replace a released installer. The branding in this manual does not establish that a new launcher is installed.

Former product name	Current product name	Preferred command
vibe-view	vibe-viewer	vibe-viewer
vibe-sketch	vibe-sketcher	vibe-sketcher
vibe-queue	vibe-scheduler	vq

The former product names and the vibe-view and vibe-sketch commands are deprecated aliases that remain supported. No removal date is scheduled. In rename-aware builds, the old commands show a deprecation notice only when stderr is interactive; redirected output remains usable in scripts. Their --help describes the transition; older published builds do not yet include these notices. The vq command, vibe-qc name, and QVF name are unchanged.

Python distribution names stay vibeview, vibesketch, and vibe-queue; Python import names stay vibeview, vibesketch, and vq. Existing pip requirements remain valid. Document schemas, MIME types, public APIs, environment variables, configuration keys, saved state and existing checkout directories retain their identities. Electron app IDs, per-user profiles and update feed addresses stay compatible. Old path names in configuration, source-backed desktop wrappers, source trust identities, and runtime generation records are compatibility identifiers, not instructions to rename those files.

Use the consolidated Vibyverse website and its vibe-qc, vibe-viewer, vibe-sketcher, and vibe-scheduler project pages. QVF remains at its authoritative GitHub repository. Pinned QVF dependencies remain at the compatible v0.6.0 release.

A repository URL update does not require moving an existing local directory. Use the clone URL supplied by your administrator for private development repositories. Public source mirrors may lag development and remain subject to their publication schedule; do not assume a rename publishes new source or artifacts. Historical release notes and published citation titles retain the names used when they were published.

Documentation reuses the Vibyverse icon and Manrope font. The bundled font is licensed under the SIL Open Font License 1.1.

A protected main or release pipeline can be explicitly selected with VIBYVERSE_DOCS_ONLY=1 to build and automatically publish documentation using the configured private deployment include. Other refs reject this mode; it cannot qualify or replace a release candidate. Runtime tests, native builds, software artifacts and desktop publication do not run in this mode. Ordinary release rules remain unchanged when the variable is absent. Deployment remains subject to the existing protected credentials and repository permissions.