Architecture
Interface Shells
The two doors onto the LisaOS core, and what distinguishes them.
An interface shell is a door onto the OS core — a wrapper that connects a model and a set of channels to the shared core over REST. Two shells exist today.
Claude Code shell
- Location — the operator's local machine.
- Channels — VS Code and the CLI.
- Model — a two-tier economy: direction seats on the faster judgment model, production seats on the higher-capacity model.
- Hardware-bound tools — a messaging bridge for context ingestion, a design-tool integration, and static analysis — tools that require local hardware or interactive auth.
Genkan shell
- Location — the always-on server.
- Channels — a terminal UI and Telegram.
- Model — a GPT-class front-door model with a Claude fallback.
- Availability — 24/7; it operates even when the local machine is off.
The same core, either way
Both shells load the same personality and governance, register with the same session registry, and share the same memory. The choice of shell is a choice of convenience and availability — never a change in who LISA is or what she can do. See Single-core philosophy.