Skip to main content

Plugins

A plugin is one thing you install to teach Celeris a whole area of work at once. Where a skill is a single learned task and a connector is one tool, a plugin is the bundle: it can bring skills, name the connectors those skills need, and carry the knowledge they read — all installed, updated and removed as a unit.

If you have used plugins in Claude or ChatGPT, this is the same idea. Install one and Celeris can suddenly do a body of work it could not before.

Installing one​

Open Settings → Plugins → Add plugin and paste a plugin's git URL, or run:

dash plugin add https://github.com/acme/acme-support-plugin

Celeris clones the plugin into its own data folder — not your working folder — so its skills are available in every conversation from then on. The card shows what it brought and whether it is ready to use.

Some plugins offer related source settings. Open the installed plugin's detail page to review them. Each source is a separate choice: turn on the source you want Lex to read, and turn on Lex when you want personal briefs. Installing a plugin does not enable a source or begin reading it.

Ready, degraded, blocked​

A plugin usually stands on connectors: a support plugin might use your help-desk and your issue tracker. Celeris checks them for you and shows one of three states on the plugin's card:

  • Ready — everything it needs is connected. Use it.
  • Degraded — the essentials work, but an optional source is missing. The card names which skills lost which source, and how to restore each. The plugin still works.
  • Blocked — something required is not connected yet. The card says what to fix first.

Press Check any time to re-run it — for example after you sign in to a connector it was waiting on.

The plugins list could not be read​

If the plugins page shows "Couldn't read your plugins. Reload to try again.", Celeris could not read the list of plugins it has installed. The list comes from the data folder Celeris keeps plugins in, so this means that folder could not be read at that moment; it does not mean a plugin is broken.

Press Reload and Celeris reads the list again; the page recovers on its own once the folder is reachable. If the message keeps coming back, the plugin folders live in Celeris's data folder (not your working folder): check that folder is on a disk Celeris can read, then start Celeris again.

Updating and removing​

  • Update pulls the latest version of the plugin. Celeris verifies the new copy before it replaces the old one, so a failed download leaves what you have untouched. Anything the plugin was keeping for you on disk is preserved.
  • Remove takes the plugin's skills back out of Celeris. Questions you answered for it are kept with your export, not thrown away, in case you reinstall.

What a plugin can and cannot do​

A plugin adds instructions — skills, knowledge, and the vocabulary Celeris uses when it talks to you. It cannot grant itself a tool, a permission, or the right to skip an approval. Installing a plugin never lowers a guardrail: a call that would ask before it ran still asks. That is deliberate, and it is what makes it safe to install a plugin someone else wrote, and safe for Celeris to keep one up to date on its own.

If a plugin names a connector you have not set up, you will see it as something to connect — never as something switched on behind your back.

Writing your own​

A plugin is a folder you can read, the same as a skill is. At its root is a small plugin.json that names the skills it ships, the connectors they use, and the files they should read. The skills are plain Markdown. There is nothing to compile and nothing to register — point Celeris at the folder and it works.

Because a plugin is just a folder and a URL, sharing one is sharing a repository. Publish it and a colleague installs it with a single paste; the niche way your team does a job becomes something anyone on it can install in a minute. Some plugins exist mainly to show off a scenario that is only pleasant because Celeris is fast — install, try, and feel the difference rather than read about it.

The full manifest reference and the rules a plugin is held to are in the plugin specification.