Voxta docs

Module sources

Where Voxta downloads modules from, adding a GitHub repository or another Voxta Cloud, and what trusting a source means.

A source is a place Voxta downloads modules from. Settings → AI Setup → Module Sources lists them. Add modules from other sources at the bottom of Add Modules and Module sources in Manage Modules' Add Modules menu open the same page. Administrators only, on Voxta Full.

Browse opens a source's page: what it offers, and install, update, revert or remove from there. Refresh there asks the source again.

The list

EntryWhat it is
Built inThe modules that come with Voxta. Always on. Lists any that failed to load.
Voxta (official)Official modules, open source and Voxta Cloud ones. Can be turned off, not removed.
A Voxta Cloud sourceAnother Voxta Cloud, added by URL.
A GitHub repositoryThird-party modules, added by owner/repo. Marked Third party, or Third party, unverified when Voxta has not reviewed its code.
Local development modulesYour own builds, and modules installed from a .zip or .dll. Manage opens Local Development Modules.

Each source shows:

  • Whether it is On or Off.
  • How many modules it offers, and how many are installed.
  • How many were downloaded but not added in Manage Modules.
  • How many updates it has (click to open them).

Per source, in its ··· menu:

  • Show pre-releases: also list pre-release versions (ticked while on). Click it again to turn it back off.
  • Turn off: Add Modules stops listing its modules, and those installed from it get no updates. They keep working. A source that is off has Turn on in place of Browse.
  • Remove removes the source and uninstalls every module downloaded from it. The confirmation lists them. The official source can't be removed.

A source that does not answer shows Unreachable, and the update banner says A module source did not answer.

Voxta Lite has no Module Sources page. It uses its built-in modules only.

Voxta Cloud sources

The official source is the Voxta Cloud this server uses. Its modules are built and published by Voxta, and every download is checked against the checksum the source lists.

Downloading needs your Voxta account: the one Voxta is signed in with, or a Voxta Cloud module's sign-in. It needs the same access as downloading Voxta itself. Pre-releases need pre-release access. Modules that need this show a Voxta Cloud badge on the source's page.

Voxta also offers the pre-release modules that were published with the exact Voxta build you run, so a test build gets the modules it was built with.

Another Voxta Cloud is added by its API URL. To download from it, set up a Voxta Cloud module signed in to that URL. Credentials are only sent over https, and only to the cloud that issued them.

GitHub repositories

Anyone can publish a Voxta module as releases of a GitHub repository. Add it by owner/repo or any github.com link inside it. Its releases are what it offers. GitHub's pre-release flag marks pre-releases.

GitHub sources come from the GitHub module, which is built into Voxta Full. For a private repository, connect GitHub in Settings → Account → Connected Accounts.

A module from GitHub is third-party. A module runs as Voxta: it can read your files, chats and API keys, use the network and install Python packages. Install it only if you trust its author.

Its modules appear in Add Modules with the others, with a Download tag and a trust tag. Installing one shows that warning on the install flow's first step, every time, before Add and continue.

What that means in practice:

  • Voxta checks that the file you download is the one the release lists.
  • Every install and every update asks you first. Their updates are never part of Update all or Upgrade all. Update them from the source's page.
  • A repository can claim the id of a module you already have, unless that module is built into Voxta. The confirmation says when an install would replace one, and where the current one came from.
  • A repository can change owner. A new release from it is new code, which is why each update asks again.

Verification

Only the official Voxta Cloud says whether a module can be trusted. What another source says about its own modules is ignored. Voxta reviews the code of the third-party repositories it knows, and its verdict shows as a tag:

TagMeaning
VerifiedVoxta reviewed this release's code. Installs without a warning.
Not verified yetVoxta verified earlier releases of this repository, not this one yet.
Not verifiedVoxta knows this repository, but verified none of its releases.
FlaggedThis release or its repository may do what you would not want. The warning has a red button.
BlockedFound malicious. Voxta does not install it.
UnknownVoxta does not know this repository.
Third partyVoxta Cloud did not answer about it.

A review is of a commit's source code, not of the zip a release ships. So a GitHub release is Verified only when its zip carries GitHub's build attestation: proof that GitHub's own runners built it from that reviewed commit. The module template attests every release. Without it, the release takes the repository's standing (Not verified yet or Not verified).

Adding a source

  1. Settings → AI Setup → Module Sources, then Add source.
  2. In Add a module source, enter a GitHub repository (owner/repo) or a Voxta Cloud's URL under Module source.
  3. Add. Voxta reads its list first, so a wrong URL is refused right away.

Then Browse its modules, or find them in Add Modules.

The same box takes a module folder on this machine (the folder button browses for one), which becomes a dev folder. Install a .zip or .dll uploads a module package. Both open Local Development Modules.

On this page