Skip to content
LVIS AI
EN|KO

Plugins

Plugins — the unit for adding what the host doesn't know about

Every domain feature in LVIS (mail, calendar, meetings, documents, corporate APIs) is split out into plugins. The host core never imports plugin-specific code (SDK type-only + CI enforced).

6 active plugins
static manifest
lvis-plugin-sdk
Plugin registration model — static manifest
Tools, Skills, events, and UI slots are all declared statically in the plugin.json manifest. There is no runtime API like registerTool/registerSkill/registerCommand in the SDK. The only runtime register API is hostApi.registerKeywords — for adding Skill trigger keywords.

Install flow

  1. Pick a plugin from the Marketplace catalog → "Install".
  2. The web page fires an lvis://install/<slug> deeplink.
  3. The host (src/main/lvis-protocol.ts) parses the URL, validates the manifest, and verifies the Ed25519 signature.
  4. A plugin permission dialog appears → user confirms → its own namespace ~/.lvis/plugins/<pluginId>/ is created.
  5. The plugin's start() is called, and hostApi.registerKeywords is registered if present.
Past → present consolidation history
  • lvis-plugin-email + lvis-plugin-calendar merged into ms-graph (archived 2026-04-28/04-30).
  • work-assistant now handles proactive work suggestions.