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).
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.Local Indexer
id: local-indexer · v0.4.11
kiwipiepy Korean morphological analysis + pymupdf4llm + FTS5 + LanceDB. Folder watching via chokidar.
Microsoft 365 (Outlook)
id: ms-graph · v0.3.28
MSAL OAuth + Electron safeStorage tokens. 31 mail + calendar tools.
Meeting
id: meeting · v0.4.18
OpenAI Whisper API (gpt-4o-transcribe) + PCM16LE 16kHz/3sec chunks.
Work Assistant
id: work-assistant · v0.7.0
10+ detectors → triggerConversation + showOverlay. Unifies mail/calendar/meeting signals.
Agent Hub Sidebar
id: agent-hub · v0.8.1
Work board sidebar + 43 tools + 5-minute polling. Talks to agent-hub.lvisai.xyz.
LGE EP
id: lge-api · v0.12.9
EP/Space/NHRS/LGenie/parking — 24 tools. openAuthWindow session + intranet DNS gate.
Install flow
- Pick a plugin from the Marketplace catalog → "Install".
- The web page fires an
lvis://install/<slug>deeplink. - The host (
src/main/lvis-protocol.ts) parses the URL, validates the manifest, and verifies the Ed25519 signature. - A plugin permission dialog appears → user confirms → its own namespace
~/.lvis/plugins/<pluginId>/is created. - The plugin's
start()is called, andhostApi.registerKeywordsis registered if present.
- lvis-plugin-email + lvis-plugin-calendar merged into ms-graph (archived 2026-04-28/04-30).
- work-assistant now handles proactive work suggestions.