Skip to content

Installed packages

Plugins is available to the installation owner. It lists installed packages, their versions, publisher, permissions and current status. A package can add providers or a panel to the running Prism instance.

  1. Obtain the package archive and its publisher’s public key from a source you trust. Native executable packages run with the operating-system permissions of the Prism service.
  2. Open Plugins and choose Trust publisher. Enter the publisher ID, Base64-encoded Ed25519 public key and permitted package namespaces supplied by the publisher. Existing trusted publishers appear below the package list.
  3. Choose Install or update and select the signed .tar.gz package. The compressed archive must be no larger than 64 MiB. An unsigned development package requires the explicit development option.
  4. Select the installed package, review its permissions and fill in its activation settings. Choose Enable to activate it.

Prism checks the archive, signature, compatibility and declared capabilities. If a package is rejected, the page shows the error. Fields marked as secret are not accepted by the public settings profile. Configure provider credentials through the normal connection and authorization pages.

Installed version is the archive currently selected for the package. Active version is the version serving its enabled contributions. Installing an update can leave the previous version active until you apply the new version and its settings.

Package activation settings take effect through Apply and activate, which starts a new activation. Some fields use a JSON editor when their public schema does not fit a simple input. Optional fields have an explicit inclusion control. Settings inside a package panel are separate: they invoke the package’s named state action.

Use Restart to replace the current worker, or Disable to stop its contributions while retaining its settings and state. The page offers separate rollback actions for the installed archive and the active version when a previous version is available. Disable a package before choosing Remove.

If another owner operation changed the package while the page was open, refresh before applying your change. The server rejects stale changes.

An active package can add tabs containing status indicators, metrics, tables, charts, settings and named actions. Prism renders these from validated package descriptions. Panel text follows the console language when the package supplies that translation, with English as its fallback.

Refresh panel reads current data. Changing, disabling or restarting the package invalidates an older open panel; refresh the package before using it again. Missing measurements are shown as unknown. Large exact totals may be displayed as text to preserve their precision.

If an action’s response is lost, its result can be uncertain. Check same action checks using the original request identity. An unresolved result remains uncertain; do not assume that the action failed or submit a new copy. Within the same open console session, a previous action remains flagged if the package was restarted or updated meanwhile. Read the current panel and acknowledge that review before submitting another action. Prism does not replay a request against a different activation. The browser keeps the check identity only in memory; after reloading the page or signing out, inspect current plugin state before submitting another operation.

The independent usage observer example includes a panel for its latest 32 observed attempts. It shows measured token subtotals, missing measurements, delivery gaps and a bounded timeline. Wallet charges, local accounting units and catalog estimates are separate. Its totals describe the retained window; they are not lifetime usage totals or replacements for Prism’s budgets.