Docs / Help — Veylum

First run

Download a package only from the configured release location and compare its full SHA-256. Review the unsigned Preview notice on the Download page.
Install, or extract the complete ZIP and open Veylum.exe.
Open Models and install an available ARC tier that fits the detected hardware.
Start a personal chat. Stop generation when needed; choose a bot or project when you want scoped context.

Install and manage ARC

The in-app Models page shows availability and hardware recommendations. Veylum downloads the pinned GGUF and verifies its digest before use. Ray, Prism, and Photon have measured Windows evidence; Laser and Spectra are selected but not offered for installation. Start smaller if loading exhausts memory, and reduce context where the app permits it.

Weights are separate downloads. Keep sufficient free space for the complete model plus temporary download files. No public automatic model updater is enabled.

Projects and workspaces

Create a project for related chats and bots. Attach a folder using the project’s folder picker to opt into workspace tools. Set reads to Allow, Ask, or Deny. After a backup restore, select the folder again before tools can use it.

Local memory

Review memories in Memory; choose personal, bot, or project scope deliberately. Edit or remove inaccurate context. Local semantic resources support memory retrieval where available; memory is not a guarantee that a model will recall every fact correctly.

Coder, tasks, and approvals

Select an opt-in Development bot in an attached Windows workspace. Read the exact change preview before approving. Confirm delete by typing the requested relative path. Changed or stale approvals must be reviewed again. The command profile runs dependency-free Node tests; it does not install packages or run arbitrary shell commands.

Use task pause, resume, and cancellation controls to manage ongoing work. Review waiting approvals in the app. Tasks preserve local state across restart but do not receive fresh permission automatically.

Enable the optional Desktop Halo in Settings to see compact activity and approval notifications. Review opens the main approval UI. Hide or disable it at any time.

Back up and restore

In Settings, create a .veylum backup before a restore or update. Store it privately; plain archives are not encrypted and contain personal app data. Model weights are not included. Enable passphrase protection for an encrypted export and keep the passphrase separately. Older 0.1.0 cannot open protected exports. The live database and rollback copies remain unencrypted. Keep your chosen model directory independently. A restore validates archive integrity and requires reauthorization of attached folders.

Mobile pairing and trust

Turn on Mobile access in desktop Settings, choose the private LAN address, save the local trust certificate, then install and trust it on your phone. Compare the server certificate fingerprint with desktop Settings. Use the expiring desktop invitation directly on the phone and approve the expected pairing request on the desktop.

Install from the desktop-hosted PWA using the browser’s Add to Home Screen option. Keep both devices on the same trusted network and the desktop awake. Revoke a device in desktop Settings to invalidate access.

Detailed pairing steps and trusted host launcher →

Troubleshooting

The model will not load

Check free storage, the verified download state, and detected hardware in Models. Choose a smaller tier or lower permitted context. Photon used reduced CPU mode on the development host. Larger tiers are not promised to fit your machine.

Mobile cannot connect

Check that Veylum is open, mobile access is running, the desktop is awake, and both devices share the same private LAN. Use the current address and port shown in Settings. Guest Wi-Fi may isolate devices. Check certificate identity and trust; do not disable TLS checking. An expired or revoked session needs a new invitation.

A certificate or trust error appears

Stop and compare the current server identity with the desktop’s displayed fingerprint. If the desktop address or local certificate changed, remove the obsolete trust certificate and install only the new certificate exported from your own desktop. Use the device’s normal certificate controls. Physical phone trust workflows require real device verification; consult the local release checklist if the platform does not accept the certificate.

An approval expires or an action is denied

Reopen the exact review in the app. Workspace changes, cancellation, stale state, and policy limits can invalidate a proposal. Recheck the folder and bot permissions; do not broaden access merely to clear an error.

Windows warns about the publisher

This preview is unsigned. Check the complete SHA-256 and release provenance. If your policy requires a signed publisher, wait for a signed build. These instructions do not bypass Windows protection.

Uninstall and data retention

Use the Windows installed-apps uninstall entry for the installer. Uninstall is configured to retain your app data. Model files live in their selected directory and require deliberate separate management.

The complete installer/uninstaller data-retention drill is still pending in final release validation. The configuration alone is not a verified installed-product result.

For the ZIP, close Veylum before removing extracted application files. Back up data first. Do not delete app data or your model directory unless you intend to remove those private files.

A good place to begin.