Overview

The shape of the system at a high level — the model, the components, and the persistent-state layer.

The big-picture view of Leif: what the system is, how it’s split, and where state lives between sessions.

Leif runs on a single FastMCP server (10.10.0.25) that exposes 270+ tools across roughly a dozen namespaces, reached by Claude over MCP through a Cloudflare Tunnel. The design is one brain, one body: Claude is the brain (conversation, planning, synthesis, judgment) and Leif is the body (tool execution, persistent state, side effects). Anything reasoning-heavy stays in Claude; anything stateful or with real-world effects lives on the Leif side.

Pages in this section

  • Getting Started — the first-session runbook: what to load before acting, the cardinal rules, and where everything lives
  • Architecture — the major components and how a request flows from Claude through the tunnel to a backend and back
  • Memory & State — Leif’s persistent-state layers (self-document, bootstrap context, notes, checkpoints, tasks, projects, commitments) and when to use each
  • Maintaining These Docs — conventions, the auto-sync pipelines, the doc-freshness discipline, and build/deploy — read it before editing pages
  • Glossary — definitions for the people, systems, programs, and jargon used across the docs