BlokeBotHelp & guides
Open the BlokeBot dashboard

Technical operations

Install and recover trusted plugins

Administer curated plugins.

The Admin page shows Bot account controls. Channel creation and channel management controls are visible. The Admin page shows Bot account controls. Channel creation and channel management controls are visible.
Open Admin to manage the Bot account and BlokeBot channels. The Plugins panel is lower on the same page.

Trusted plugins

Current plugins do not use a capability grant or security sandbox.

  • A curated plugin has the same filesystem access as the BlokeBot service account.
  • A curated plugin has the same process access as the BlokeBot service account.
  • A curated plugin has the same network access as the BlokeBot service account.
  • Only a BlokeBot administrator can install a curated plugin.
  • Only a BlokeBot administrator can update a curated plugin.
  • Only a BlokeBot administrator can restart a curated plugin.
  • Only a BlokeBot administrator can remove a curated plugin.

Plugin permissions

A curated package can contain any reviewed declared payload for its supported targets. Supported payload types appear below.

Lua 5.4 is the only plugin entrypoint that BlokeBot manages. Other payloads and their dependencies remain the plugin's responsibility.

Each active plugin uses one worker process. The worker is an availability boundary, not a security sandbox.

  • BlokeBot checks declarations.
  • BlokeBot checks targets.
  • BlokeBot checks archive paths.
  • BlokeBot checks links.
  • BlokeBot checks collisions.
  • BlokeBot checks size limits.
  • Native files.
  • .NET files.
  • WebAssembly files.
  • Browser files.
  • Media files.
Linux
linux-x64 and linux-arm64
macOS
osx-arm64
Windows
win-x64 and win-arm64

Marketplace catalog

An entry selects a compatible declared version and one Git tag. Plugin identity never contains a commit SHA.

The community link queue is a local reference example. Its catalog entry and tag are not public.

Saved snapshot
Search uses the last valid catalog snapshot and does not wait for GitHub. Offline search can use this snapshot.
Refresh failure
Search keeps the previous snapshot. Admin shows its age and the refresh failure.
No snapshot
The marketplace is unavailable until one refresh succeeds.
Package download
Install and Update still need GitHub. BlokeBot does not cache package archives.

Install and configure

  1. Open Admin.
  2. Find Plugins.
  3. Review the package source.
  4. Review the declared payloads.
  5. Review the supported targets.
  6. Review the version and tag.
  7. Select Install.
  8. Enter the generated installation settings.
  9. Enter each required protected secret.
  10. Save the settings before you enable channel features.

Update the tag

Update is always a manual administrator action. It downloads and validates the current package at the selected tag.

BlokeBot stops the current plugin work before it applies the update.

The old version stays active during non-durable preparation. If durable migration starts, the old code can never resume.

Correct the package or tag. Then start a new administrator action.

  • A validation failure faults the selected installation.
  • A migration failure faults the selected installation.
  • An activation failure faults the selected installation.

Recover a worker fault

BlokeBot performs one automatic restart after an unexpected worker exit. A second unexpected exit faults the plugin.

  1. Open Admin.
  2. Read the latest operation message.
  3. Correct the reported problem.
  4. Select Restart.
  • The problem can be in the package.
  • The problem can be in a dependency.
  • The problem can be in the host.

Remove a plugin permanently

Remove permanently deletes all plugin installation state:

  • Remove leaves no unavailable page.
  • Remove leaves no unavailable flow.
  • Remove leaves no latest lifecycle outcome.
  • Installed package files.
  • Installation settings.
  • Feature settings.
  • Configuration.
  • secrets.
  • Schedules and the private SQLite database with its sidecar files.
  • Plugin definitions and automation ledgers.
  • dependent flows and dependent nodes.
  • Run history and source receipts.
  • the marketplace installation receipt and plugin invocation context.

Plugin package reference

The operator guide does not define plugin APIs or package schemas. Use the generated author reference for those contracts.