Native desktop host
An Electron-based app brings signals from mail, calendar, meetings, documents, and internal APIs into one place. Available for macOS, Windows, and Linux.
Plugin-native desktop AI · approval-first
Quiet observation,
precise suggestions,
your approval.
LVIS reads signals from your mail, calendar, meetings, documents, and internal APIs, and only speaks up at the right moment. Every write action starts with your approval.
- Plugins
- 6+
- Workspace
- Up to 4 tiles
- Run policy
- Approve, then run
- Local-first
- On-device
The App
A work assistant that runs on your own PC.
LVIS is a desktop AI work host. Reading signals, drafting proposals, and carrying out results all happen on your device. Your PC is the stage — not the cloud.
Local-first · on-device
The local indexer indexes documents on your PC right on the device. Document contents never leave your machine, and signals are first classified read-only.
Plugin architecture
Add only the plugins you need, each isolated in its own runtime. Nothing is forced on you, and swapping one out after review is easy.
Approval-first execution
Observation and suggestions happen quietly, while write actions pass through a risk-labeled approval gate. Execution always begins with your decision.
- Supported builds
- macOS · Windows · Linux
- Default download
- Windows 10+ · x64
- Run policy
- Approve, then run (high-risk actions require a reason)
- Data boundary
- Local indexing · contents kept private
A Day with LVIS
Follow the flow of a day, together.
It quietly watches every signal as it comes in, and only shows itself at the right moment.
08:00
work-assistant · ms-graph
Before your day begins, today's briefing is ready.
LVIS combines yesterday's mail, today's schedule, and still-open tasks into a morning briefing. See what to prepare before meetings and which emails need a reply, at a glance.
09:14
ms-graph · work-assistant
Before an email becomes a meeting.
LVIS reads a new email's headers and body to identify a meeting request. It checks open time slots and rooms too, so you can reply, book, and add it to your calendar in one click.
10:55
meeting · work-assistant
Right before a meeting, a prep card opens first.
15 minutes before a scheduled meeting, a prep card automatically surfaces the schedule, agenda, video link, and a summary of the last meeting. It never exposes the body text, and the OS notification stays a short one-liner.
11:47
meeting · work-assistant
When a meeting ends, the summary is ready first.
LVIS detects the meeting's end, transcribes it, and automatically organizes a summary and action items. It estimates owners and deadlines and moves them straight to the kanban work board built into the app.
14:32
work-assistant
One more check with you before it runs.
LVIS combines the afternoon's signals into kanban cards for tomorrow's to-dos. Writing to the board also has to pass an approval dock. The higher the risk, the clearer it's shown.
15:30
work-assistant · meeting
Want help putting together your weekly report?
LVIS gathers this week's meeting summaries, completed actions, and next week's schedule into a weekly report draft. The draft follows your team template's tone and length, and whether to send it is always your call.
17:00
work-assistant
Ready to wrap up the day?
LVIS walks you through checking tomorrow's schedule, tidying up unfinished tasks, and writing follow-up notes in one flow. Once the wrap-up check is done, LVIS goes quiet too.
20:00
local-indexer · work-assistant
While you're away, LVIS keeps working.
When idle time is detected, LVIS quietly handles new document indexing, meeting summary enrichment, and email sorting. It yields the moment you return — closer to background cleanup than active work.
Workbench
Several conversations side by side, in one window.
In work mode the conversation area splits into as many as four tiles. Each tile holds its own conversation and its own work panel, so looking closely at one does not stop the others.
Split left/right, or top/bottom
Pick the direction from the tile's split menu. Any tile can be closed or maximized on its own, and a conversation is only ever open in one tile at a time.
A work panel per tile
The panel keeps one card shape at every width and takes the full height of its tile. Files, web sources, and sub-agents sit behind tabs, and the launcher shows which tool is running right now.
Cards stay in their own tile
Overlay cards, question cards, toasts, and MCP cards appear only in the tile whose conversation raised them. What happens next door does not cover the screen you are reading.
The sidebar tells you where things stand
Each conversation carries a responding dot and a mark for turns you have not read yet. The list reveals more as you scroll, and conversations are grouped by project.
Return to a message you sent
Your own message card shows when you sent it, and “Return here” puts that message back in the composer and discards what came after it. A reply that went the wrong way no longer means retyping from scratch.
Choose a model on the card, save it there
Provider cards in settings save on the card itself. An endpoint field appears only for providers you point somewhere yourself, and the model list is fetched from the provider. For OpenAI, sign in through the browser, use a device code, or paste an API key.
In the composer — a send that was refused says so, and while a turn is running Enter queues your next message while ⌘↩ interrupts the one in flight.
Desktop App
Pick the build for your OS.
Grab the macOS, Windows, or Linux build straight from GitHub Releases. The button always points at the latest build. See all releases
Windows
Windows 10+
Installer · x64
Latest build · availableLogin and the first screen after install continue in the install guide.
First launch after install
Because the app is unsigned, Microsoft Defender SmartScreen shows a warning on first launch.
- 1
Run the installer you downloaded.
- 2
When the “Windows protected your PC” dialog appears, click More info.
- 3
Click the Run anyway button that appears.
Alternative: right-click the installer → Properties → General tab, check “Unblock,” and the warning won't appear.
Architecture
The user is always on top. Below, the host and isolated plugins do the work.
Signals flow up from the bottom, and decisions flow down from the top. Every layer is separated by an explicit permission boundary.
User
Decision · approval · keyboard input
High-risk tools pass only with a stated reason and explicit approval.
LVIS Core
Host · approval gate · tool runtime · audit
Every tool call goes through policy evaluation, a permission check, and an audit log.
Plugins
Isolated runtimes · Host API access only
Plugins can't touch each other's data directly — they only call the Host API with explicitly granted permissions.
Microsoft 365MeetingLocal IndexerWork Assistant
Signals
External signals · local documents · internal APIs
Mail · calendar · Teams · meeting recordings · local folders · LDAP · internal facility APIs.
↑ Decision · approval flow · ↓ Signal · data flowRead the architecture docs
Surfaces
Two surfaces, one flow.
The app gathers signals, the Marketplace adds capabilities, and the work board inside the app records the results.
Marketplace
Discover and install plugins.
Check versions, distribution packages, and install policies in one place. The app downloads, verifies, and registers the plugins you need through this catalog.
Open the marketplacePersonal work board
Organize your work on a kanban board.
To-dos, approval requests, and daily reports your agents create are collected on a personal kanban board inside the LVIS app. See the flow at a glance across To do · In progress · Done — execution always starts with your approval.
A personal board built into the LVIS app.
Roadmap
Ends July 31From static integrations to autonomous collaboration.
Plugins evolve from simple tool-calling modules into connectors and autonomous sub-agents. We're rolling out six vision axes across v1 through v4. Timing isn't finalized yet.
- 01
Plugin → Connector + UI
We're going beyond tool calls, expanding into first-class connectors that offer bidirectional streaming UI, their own workspace, and interactive widgets.
- 02
Plugin = Sub-agent
Plugins act autonomously with their own prompts, tool sets, and decision loops. Delegated scope is isolated by the agentApproval permission scope.
- 03
Idle-time Intelligence
Detects OS idle state to handle indexing, summarizing, and briefing prep in spare time. Yields immediately the moment the user returns.
- 04
Capability Pack
Bundles today's four separate catalogs (plugin · agent · MCP · skill) into a single deployment unit. Users only need to install once.
- 05
Trigger DSL
Extends shutdown/schedule triggers into event trees, condition combinations, debounce, and weighting. Routines become a small workflow engine.
- 06
Hooks — Lifecycle + Interceptor
Extends today's start/stop-only lifecycle to install, activate, tokenRefresh, pre/postToolCall, and onPermissionGranted. Establishes a standard point where external code can safely hook into the flow.
v1
Laying the foundation
- Connector UI
- Capability Pack v1
- Trigger DSL v2
- Plugin Lifecycle Hook v1
v2
A step toward autonomy
- Plugin-as-Sub-Agent
- Idle-time Intelligence
- Interactive widgets
- Host hook surface
v3
An opening host
- Local LLM Fallback
- Federation v1
- Automatic external MCP classification
v4
The next stage of LVIS
- WASM Sandbox
- ROI Dashboard
- Mobile · Raycast · VSCode Companion
This roadmap is directional. Detailed milestones, code entry points, and status are updated with quarterly retrospectives in the roadmap docs .
Pilot
Start with one small team, then scale to the whole org.
Validate the flow with a single team's signals, then grow the Marketplace catalog as you expand across the organization. Connecting mail, calendar, and meetings one step at a time is plenty to start.