LYST

---

You describe a question or a piece of work. Lyst plans it, runs it on approved data definitions with SQL and Python, verifies the result independently, and returns a decision-ready answer with every query, check and assumption behind it. It is judged by completed, verifiable work, not by conversation: every number comes from a query, whether or not a model is involved.

Why Lyst

• Verified, not plausible. Every figure is recomputed independently from approved data, and each answer shows the checks it passed, the data and version it used, and the assumptions it made.
• Does the work, asks before it changes anything. Lyst plans, investigates, prepares recurring work and reacts to events on its own, inside limits you set; anything consequential waits for a person.
• Yours to run. Self-hosted, encrypted at rest, works with OpenRouter or a local model (or none), open source under AGPL-3.0.

Contents: Quick start · Tour · What Lyst does · AI SDK · Models · Security · Commands · Development · Documents

Quick start

You need uv on macOS or Linux.

git clone https://github.com/MoRohn/lyst.git && cd lyst
uv sync --all-extras
uv run lyst start --demo

One command initialises encryption (the master key goes into the OS credential store), seeds the Northwind demo workspace, starts the engine and the interface, and opens http://lyst.localhost:8501:

Lyst is running at http://lyst.localhost:8501
  Engine     http://127.0.0.1:8770
  Interface  http://lyst.localhost:8501
  Data       ./var
  Demo       the Northwind workspace is ready; try "Why did operating margin decline last quarter?"
Ctrl-C stops it. From another terminal: `lyst status`, `lyst stop`.

uv sync installs Lyst into the project's .venv, so run commands through uv run from the checkout (a bare lyst is "command not found" unless you first source .venv/bin/activate). From any terminal in the checkout:

uv run lyst status          # is Lyst running here, at which address, under which PIDs (--json for scripts)
uv run lyst stop            # stop the Lyst that `lyst start` launched; never touches processes it didn't record
uv run lyst start --check   # preflight: Python, data folder, encryption key, database lock and ports, opening no database

lyst start is safe to run again. If Lyst is already running here it opens that one instead of starting a second; if a default port is busy it moves to the next free one and says so (an explicit LYST_PORT or LYST_UI_PORT that is busy is a clear error); and if another program holds the data open it names that program's PID instead of failing with a traceback. Ctrl-C in the starting terminal stops everything cleanly.

Then ask: "Why did operating margin decline last quarter?" Lyst finds that operating margin fell from 36.0% in Q2 2026 to 32.5% in Q3 2026, that EMEA's own margin drop (36.8% to 24.0%) explains it, reconciles the bridge exactly, and saves the analysis so it can be rerun for any period. That story is planted in the demo data (src/lyst/demo.py) so the tests can check that Lyst recovers it.

No model is needed to try it. With none configured, Lyst runs on rules and templates; adding one improves understanding and wording, never the numbers.

以上为 README 的开头部分。其余内容请阅读原文。 查看完整 README ↗