Lians-ai/Lians

Quickstart ·
Why Lians ·
ContinuityBench ·
Install ·
Docs ·
Issues
Lians Guard
**The current-state and completion guard for AI coding agents.**
Lians recovers interrupted agent work, rejects stale task state, and blocks
done until the current task is ready for human review.
> Your agent can forget the chat. It cannot forget what is finished, what
> changed, or what still has to pass.
- **Recover.** Resume a bounded current task across supported Claude Code and
Codex sessions.
- **Reject stale state.** Bind checkpoints to current repository and task state
so old evidence is not silently reused.
- **Guard completion.** Separate measured evidence from an agent's own claims
and keep the gate closed while work is missing, unknown, failed, or blocked.
- **Require review.** READY FOR HUMAN REVIEW is a handoff to a person, never a
claim that the work is correct, approved, or safe to deploy.
- **Stay local.** The free recovery path needs no Lians account, AI password, or
provider API key.
Lians works with your existing AI account and editor. It does not replace your
model, Git, CI, repository instructions, or human review.
Two layers, one agent loop
The open-source **Lians Guard** layer lives inside Codex through MCP, skills,
hooks, and repository state. It remembers corrections and exposes evidence
without taking over the model. The optional **Lians Mission Control** beta is
the local control layer: give it one mission, let it choose a bounded Codex
route, and require a real verifier before it returns PASS.
On supported Codex versions, one Mission Control mission now uses one Codex
app-server thread instead of starting a new process and replaying a summary for
every stage. Codex still owns authentication, tools, sandboxes, and execution;
Lians owns the durable mission, usage policy, and receipt. App-server is
currently experimental, so the one-shot adapter remains available.
Inspect the Mission Control source, read the
bridge boundary, or follow the
external proof-gate protocol.
One clear result after every agent session
The trust model is deliberately strict. measured_local, measured_ci, and
human_confirmed evidence can satisfy a criterion. agent_attested and
inferred_activity records remain useful context but cannot open the review
gate. An agent cannot promote its own checkpoint into a trusted class. Trusted
CI evidence requires an exact GitHub attestation and commit match plus an
interactive check-to-criterion mapping; human evidence requires interactive
confirmation. Read why Lians exists, the full
Lians Guard product contract, and the current market
pressure test.
Try it in two minutes
Choose the AI tool you already use:
| Tool | Fastest setup |
|---|---|
| Codex app, CLI, or IDE | One command |
| Claude Code | Two plugin commands |
| Cursor | One-click MCP install |
| Other MCP clients | Minimal MCP setup |
For example, after installing uv, connect Codex with:
Restart Codex, then save one safe project fact and recover it in a fresh chat.
Local memory is stored in ~/.lians/mcp.db by default. This is the available
free recovery path; the full Guard workflow is currently a developer preview.
Follow the complete quickstart for setup, recovery,
correction, deletion, and the Guard preview boundary.
What a fresh coding agent receives
Lians can generate a bounded project handoff instead of replaying a transcript:
The handoff is derived from current Lians state, not a manually maintained
summary. Agent-reported work remains visible without being mislabeled as
verified completion.
Why this is not another generic memory layer
Native memories are convenient when work stays inside one product. General