Release status & requirements

Checked 5 November 2026. Choose the release and deployment scope your organization has approved.

Make an informed deployment decision

Product availability, verified download integrity and full production acceptance are separate checks. The table describes the scope verified for each product; it does not certify every customer environment. Preview components and legacy installers do not acquire newer capabilities because another product has been updated.

ProductReleaseDeployment status
Sophie BrowserWindows 0.1.22 / Linux 0.1.19Platform-specific validation

Download and updater integrity checked. Windows publisher signing and a fresh complete platform acceptance remain release gates.

ViAgen7Online serviceControlled validation

Sign-in required. Entitlement, quota and workspace permission checks pass; complete customer build, publish and recovery acceptance is separate.

Vigthoria CodeWindows 2.0.166Engine upgrade required

Delivery and update discovery checked. A supported editor/Electron foundation and Windows publisher signing must qualify before general deployment.

Vigthoria CLI1.13.52Scoped checks passed

72 hermetic suites and a fresh install passed. Live account, selected model, subscription and provider availability still apply.

Vigthoria WorkbenchSigned Windows evaluation 2.3.2-preview.3 / legacy direct 2.2.2Signed evaluation; Windows installation checked

Public publisher signing is operational. Native signatures, upgrade, uninstall/reinstall, 506 companion hashes and a fictional installed private-AI workflow passed in a Windows 11 validation environment. Normal recipient T01, organisation policy and broader feature acceptance remain separate. Store update certification is pending.

Vigthoria AI VSIX2.2.164Scoped checks passed

New standalone release: cryptographic delivery, corrected guard, lock identity, all 35 packaged desktop test files and actual isolated Windows installation/activation passed. Code 2.0.166 retains bundled 2.2.163; a supported editor is still required.

Web IDE (Coder)Browser serviceControlled validation

Anonymous workspace access is denied. Per-account entitlement, isolation, restore and capacity acceptance apply.

DevTools Bridge2.0.0-preview.1 / legacy npm 1.2.0 withdrawnPaired local evaluation; internal research migrated

Authenticated public-page research is deployed internally. The signed local v2 preview passes scoped Linux, Windows and browser tests. Its protocol differs from legacy Code/CLI clients; full customer interoperability remains a release gate. Public cloud access stays closed.

Chrome companion2.0.0-preview.1 evaluation / 1.0.0 withdrawnReviewed capture evaluation

The v2 companion uses explicit pairing and preview/edit/send, without all-sites access or automatic capture. A synthetic local-page browser flow passed; external-page activation, store distribution and full customer journeys remain unqualified.

Windows Desktop Bridge0.1.4 restricted previewExplicit local evaluation

Private pairing and capture/control/execution are separate permissions. No automatic cloud fallback. General desktop-control acceptance is pending.

Android Control BridgeADB workflowDevice validation required

This is a documented Android Platform Tools workflow. A real device, USB/wireless pairing, permission revocation and reconnect tests are required.

Vigthoria TablesWorkbench componentPreview

Validate formulas, import/export fidelity, recovery and representative spreadsheets before adopting it for business records.

Vigthoria DocumentsWorkbench componentPreview

Validate document import/export, pagination, accessibility and recovery against the documents your organization uses.

Vigthoria PresentationsWorkbench componentPreview

Validate slide import/export, media, fonts, presenting and recovery on the target Windows environment.

Developer AI APIPre-release gatewayPublic endpoint closed

The public API remains closed during pre-release validation. Product-specific AI access follows its own authenticated route and service limits.

Vigthoria Voice AndroidAPK package 1.0 (legacy filename 1.1.0)Device qualification required

APK signature and HTTPS bytes verified. Filename and installed version differ. Fresh microphone, identity, permission, upgrade and recovery checks are required.

Vigthoria AGI AndroidAPK package 1.0 (legacy filename 2.1)Device qualification required

APK signature and HTTPS bytes verified. Filename and installed version differ. Verify current service compatibility, permissions, account isolation and update behavior before deployment.

UsGuard Android1.1.0Device qualification required

APK signature and HTTPS bytes verified. A current real-device workflow, permission, data-flow, update and recovery acceptance is still required.

Before using confidential material

Agree the processing mode, approved data sources, access policy, exports, logging and recovery with your organization. Workbench's isolated private workflow is distinct from online Assistant, development tools and provider integrations. Do not assume every ecosystem feature keeps its input on the device.

Workbench documentation · Workbench help · Product guides

Legacy Android hand-offs

The Voice, AGI and UsGuard short links lead here while current device qualification is pending. Cryptographic package verification passed. Voice and AGI filenames do not match the version displayed by their Android package manifests. Do not treat a filename as evidence of a newer installed application. No Android device was connected during this audit.