Vigthoria Workbench

Microsoft Store — package 2.3.2.0

Package 2.3.2.0, containing Workbench 2.3.1-preview.6 and CLI 1.13.52, has been submitted for the free public release. Microsoft certification, signing and publication are pending. The existing signed 2.3.1.0 Store release remains available to invited pilot accounts. Workbench includes Vigthoria Tables, Documents and Presentations; it requires Windows 11 x64 and WebView2.

1. Save your work and quit an existing Workbench installation before starting the Store edition.
2. Wait for public access to be confirmed here before installing. Existing invited testers can continue using the private pilot listing with their approved personal Microsoft account.
3. After the update is approved, expect Store package 2.3.2.0 and app version 2.3.1-preview.6. The existing pilot remains package 2.3.1.0, app 2.3.1-preview.1, until that update is delivered.
4. Check that your projects and settings are present, then verify the tools you use. Retain your previous project files until migration is checked.
5. For updates, use Microsoft Store → Library. Optional CLI installation or repair remains a separate control in Workbench and requires Node.js/npm.

An older direct EXE is a different distribution channel; Store approval does not sign that file. Keep Windows protection enabled and use the Store installation for the signed release.

Local context and the CPU semantic helper do not enable production GPU offload or commercial compute rewards. Protected Vigthoria model weights remain on Vigthoria infrastructure.

Legacy Windows direct installation — 2.2.2

1. Download Vigthoria-Workbench-Windows-Setup.zip
2. Extract the ZIP (right-click → Extract All)
3. Double-click Install-Vigthoria-Workbench.bat — do not open the .ps1 in a text editor
4. The installer downloads the app and sets up a desktop shortcut; Workbench opens when done
5. The setup ZIP includes and verifies Vigthoria CLI 1.13.45; confirm the detected version in Settings → Updates after launch. The direct EXE and portable app also include this archive; use Install / repair verified CLI to install it.

Start with your ecosystem

1. Account & runtime: sign in to your Hub account. General account access does not require Coder. Each service checks its own subscription. Read your wallet balance here; Manage credits opens Hub's existing purchase flow.
2. Projects & agents: choose a local project folder and workspace preset. Connect Coder in Settings for V3 agent tasks. Terminals, reports, files, Hyper-Loop and templates remain available.
3. Creative studio: develop a Creative V2 brief or prepare a media request with your agent. Choose your provider/model, review the request and start generation. Preview completed assets in Workbench.
4. Campaigns: open Operator to prepare captions, branding, assets and the calendar. Pair the local publishing console, connect the intended social accounts, approve the schedule in Operator, then run it locally.
5. Activity: inspect agent receipts, media jobs and publication results. Interrupted or uncertain submissions require review before another attempt.

Keep an approved schedule running

On Windows, Run/Pause is restored after restarting Workbench. Closing the worker window keeps it running. When enabled, closing the main window keeps Workbench in the system tray. Quit Workbench stops execution. The computer must remain awake and online.

V4 runtime

V4 requires a separately installed runtime, its Python dependencies, and a configured gateway. Set these in Settings. Each brief launches one task in the selected project; Stop ends it. Restarting the app does not repeat the task. Runtime detection alone does not verify model availability.

Coder sign-in and CLI repair

Hub sign-in connects your ecosystem account. V3 agent tasks use a separate Coder session and an eligible Coder subscription. The normal Login button opens the in-app form; background session checks do not open terminals. Use Settings → Updates → Install / repair verified CLI for the version bundled with your app: 1.13.52 in the new Store submission, or 1.13.45 in legacy 2.2.2. On an existing installation, run vigthoria update to obtain CLI 1.13.52 or later for the current model choices, then sign in to Coder. App updates preserve existing workspace and settings records.

Update an existing installation

Microsoft Store: use Store → Library to check for updates. Store installations do not use the direct EXE updater.

Direct installation: open Settings & updates → Check for updates → Download & install. Workbench verifies Vigthoria's release signature and download integrity, then reopens after installation. This verification is separate from Windows publisher signing. Your workspaces and provider connections remain available. The separate Install / repair verified CLI control updates agent tooling.

Bring your own media provider

1. In Settings → Your media providers, add an OpenRouter, OpenAI-compatible Images API, fal, or Replicate connection.
2. Choose your provider model and enter your own API key. Keys are kept in the operating system credential vault.
3. Open your Creative studio. Choose image, video, or audio where the selected provider supports it; review the prompt and model options before generating.
4. Let the agent prepare a media request, then import and review it in Creative studio. Completed files and receipts are saved in your workspace for later editing and publishing.

Generation uses your provider account and its pricing. Asynchronous jobs can be refreshed after restarting Workbench. An interrupted submission is not automatically repeated; check your provider dashboard before submitting again.

Linux credentials require an unlocked Secret Service-compatible keyring. V4 text-agent mode also requires a compatible V4 runtime installed on the computer; media generation in Creative studio does not require that runtime.

Linux

Download the .deb package from the products section, then:

Launch Vigthoria Workbench from your application menu.

Requirements

• Microsoft Store: Windows 11 x64 with WebView2. Direct 2.2.2 release: Windows 10/11 x64 with WebView2.
• Node.js/npm for agent, login, and Hyper-Loop tools; the Windows setup ZIP attempts Node.js LTS installation when needed, then installs the current CLI. Workbench 2.2.2 bundles CLI 1.13.45.
• Linux amd64: install the .deb from the products section