Skip to content
LVIS AI
EN|KO

Architecture

LVIS system at a glance

LVIS is structured around four layers — the Electron host, the plugin runtime, local storage (~/.lvis), and servers — all operating on the same user signals. Every domain feature is split out into plugins, and the host never imports domain-specific code (enforced at the CI stage).

static manifest
no fallback
Desktop Host

Electron host

App.tsx · MainToolbar · ChatViewMessageQueuePanel · SessionTodoPanelReviewer (risk-classifier)Tool Registry · ConversationLoopRoutineEngine (shutdown · schedule)
Plugin Runtime

boot/steps/plugin-runtime.ts

ms-graph (mail+calendar)local-indexer (kiwi · pymupdf4llm · LanceDB · FTS5)meeting (Whisper STT)work-assistant (proactive · detectors)internal portal plugin (24 tools)
Storage

~/.lvis/ (0o700 / 0o600)

sessions/routine/audit/<YYYY-MM-DD>.jsonlplugins/<id>/secrets/permissions.jsonsettings.jsonmemories/MEMORY.md
Servers

Marketplace · external

Marketplace (FastAPI · plugin/agent/mcp/skill catalog)MCP servers (external)ms-graph · internal portal · internal search (external APIs)

↑ decision · approval flow  ·  ↓ signal · data flow — every layer is separated by an explicit permission boundary.

Data flow — one user message turn

  1. 01

    User input

    User input → ChatView.
  2. 02

    Scope selection

    The Host selects enabled plugin scope from explicit activation and carried session state.
  3. 03

    Tool call decision

    The model uses eager Tool schemas or promotes deferred Tools through tool_search.
  4. 04

    Reviewer evaluation

    Decides auto / card / dialog from the grid of tool RiskLevel × Category × the user's grant.
  5. 05

    Execution

    On approval, the plugin handler runs (cross-plugin calls possible via callTool).
  6. 06

    Response streaming

    Tool results + thinking tokens → LLM context → streamed into the chat body.
  7. 07

    Audit logging

    Every step is appended to ~/.lvis/audit/<YYYY-MM-DD>.jsonl.
Architecture doc consistency
Every implementation is rooted in lvis-app/docs/architecture/architecture.md (v4 Final), and no pattern, structure, or approach that contradicts the document is introduced — LVIS Project CLAUDE.md rule.