Lians Agent Memory

Name: Lians Agent Memory
Author: Lians-ai

by Lians-aiversion 0.5.0i★ –iRuns on your computer

Registry nameio.github.ebeirne/lians

Install

Overview

Description from the maker (original English)

Bitemporal memory for AI agents with point-in-time recall and tamper-evident audit history.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi0 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory
You need to fill in: LIANS_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 0 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: LIANS_URL, LIANS_API_KEY, LIANS_AGENT_ID, LIANS_LOCAL_DB, LIANS_NAMESPACE

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "lians": {
      "command": "uvx",
      "args": [
        "lians-sdk"
      ],
      "env": {
        "LIANS_URL": "your-value",
        "LIANS_API_KEY": "your-value",
        "LIANS_AGENT_ID": "your-value",
        "LIANS_LOCAL_DB": "your-value",
        "LIANS_NAMESPACE": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add lians --env LIANS_URL=your-value --env LIANS_API_KEY=your-value --env LIANS_AGENT_ID=your-value --env LIANS_LOCAL_DB=your-value --env LIANS_NAMESPACE=your-value -- uvx lians-sdk

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "lians": {
      "command": "uvx",
      "args": [
        "lians-sdk"
      ],
      "env": {
        "LIANS_URL": "your-value",
        "LIANS_API_KEY": "your-value",
        "LIANS_AGENT_ID": "your-value",
        "LIANS_LOCAL_DB": "your-value",
        "LIANS_NAMESPACE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "lians": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "lians-sdk"
      ],
      "env": {
        "LIANS_URL": "your-value",
        "LIANS_API_KEY": "your-value",
        "LIANS_AGENT_ID": "your-value",
        "LIANS_LOCAL_DB": "your-value",
        "LIANS_NAMESPACE": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

LIANS_URL env
Optional base URL of a hosted or self-hosted Lians server; omit for local SQLite mode
LIANS_API_KEY secret env
API key with read and write scopes
LIANS_AGENT_ID env
Agent identifier used as the memory namespace
LIANS_LOCAL_DB env
Local SQLite path used when LIANS_URL is omitted
LIANS_NAMESPACE env
Local tenant namespace

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

! Caution
Maker matches the repo
The publisher (ebeirne) is not the repo owner (Lians-ai); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7275 servers in this category
Published to the registry more recently than 27% of the other 7275 servers in this category
Basic checks equal to or better than 30% of the other 7275 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Lians Agent Memory safe?

It passed 0 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: LIANS_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.5.0) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated yesterday

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 21 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Recover the task. Reject stale state. Block unsupported done.

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

RECOVERED

Task: Fix OAuth callback handling Next: Re-run the callback integration test

STALE Reason: The authentication requirement changed after this checkpoint

BLOCKED Missing: OAuth callback integration test Untrusted: "tests passed" was reported by the agent, not measured

READY FOR HUMAN REVIEW Measured locally: callback tests passed Measured by CI: required checks passed

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:

codex mcp add lians --env LIANS_MCP_ENABLED_TOOLS=remember,recall,list_memories,correct_memory,forget_memory -- uvx --from "lians-sdk[mcp]" lians-mcp

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:

Reported complete; verify:

migrated the orders API to /v2/orders

Still open:

verify the migration against current Git state
update documentation

Decisions:

keep pytest

Changed:

/v1/orders is stale; use /v2/orders

update documentation before touching unrelated UI

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 memory is no longer a scarce category. Lians uses local memory for recovery, then focuses on the expensive gap: current task state and evidence-backed readiness.

The current competitive landscape pressure tests this position against native Claude Code, Codex, Cursor, GitHub Copilot, Entire, Factory, and AI review workflows.

Approach	Best fit	Boundary
Native tool memory	One AI tool, minimal setup	Usually stays inside that vendor
`AGENTS.md` or `CLAUDE.md`	Stable repository instructions	Must be maintained manually
Transcript replay	Reconstructing one conversation	Large, noisy, and may revive stale decisions
Free Lians recovery	Resume current project context across supported tools	Requires a local connection to each tool
Lians Guard	Detect stale state and gate readiness with typed evidence	Team workflow is still in developer preview

Lians is not claiming that every project needs a separate memory layer. See the honest comparison and decision guide.

Project status

Lians is under active development. Available recovery features and preview Guard features are separated here so the repository does not imply a production guarantee that does not exist yet.

Capability	Status
Local memory through MCP and Python	Available
Codex, Claude Code, and Cursor local recovery setup	Available
Inspect, correct, and confirmed permanent deletion	Available
Bounded context and signed selection receipts	Available
Automatic Claude-to-Codex project handoff	Beta
Typed evidence and evidence-backed task gate	Developer preview
Local Git workspace fingerprint on checkpoints	Developer preview
Automatic stale evidence invalidation	In development
Attested GitHub Actions evidence intake	Developer preview
Local Guard reporting	Developer preview
Shared team queue	Planned
Cross-platform clean-install CI	Required by the new Guard workflow; first hosted run pending
Guided desktop installer and local control center	Release candidate
Mission Control Protect-versus-Maximum beta	Candidate; proof gate preregistered
Persistent one-mission/one-Codex-thread bridge	Beta; app-server is experimental

The macOS and Windows desktop builds remain release candidates pending platform signing and notarization. See the desktop preview boundary.

Current evidence

The included Claude-to-Codex continuity fixture recovered 10/10 expected facts, exposed 0 stale facts as current, and produced a 231-token handoff. These are bounded beta results, not a promise that every live coding session extracts perfectly. Run the experiment.

The developing ContinuityBench v0.1 publishes the proposed cross-agent, freshness, correction, erasure, provenance, and boundedness test contract. Its current Lians fixture is evidence for that fixture only; it is not presented as a completed competitor leaderboard.

A separate live test saved a synthetic project fact through Cursor, recalled it in a new Cursor chat and a fresh Claude Code session, and confirmed it was gone after deletion. Read the test method.

The Guard correctness benchmark exercises missing evidence, unknown criteria, failed constraints, blockers, stale updates, and drift signals. It is a local, deterministic test of the configured policy, not proof of semantic correctness or a production outcome. Run packages/lians-easy/benchmarks/task_contract_correctness.py to inspect the cases.

Build with Lians

Use the local Python SDK inside an application:

pip install "lians-sdk[local]"

from datetime import datetime, timezone

from lians import LocalLiansClient

memory = LocalLiansClient(db_path=".lians/memory.db") memory.add( agent_id="my-agent", content="The project uses Python 3.12 and pytest.", event_time=datetime.now(timezone.utc), )

result = memory.recall( agent_id="my-agent", query="Which Python version and test runner should I use?", )

See the install guide for TypeScript, Go, Java, C, framework integrations, and self-hosting.

Running a class, club, hackathon, or campus developer group? Use the student and community kit. Contributors and package integrators can start with Supported paths and repository status.

Advanced capabilities

Lians also includes tools for project-scoped agent handoffs, signed selection and review receipts, local research and browser briefs, temporal reconstruction, lineage, information barriers, confirmed erasure, and bounded formal checks. These capabilities are useful for advanced or governed deployments but are not required for the starter memory workflow.

Memory engine
Cross-agent continuity experiment
Agent-work verification
Security model
Community and managed product boundary
Supported paths and repository status

Development

git clone https://github.com/Lians-ai/Lians.git

cd Lians python -m pip install -e ".[dev]" python scripts/test_all.py

Read CONTRIBUTING.md before opening a pull request. Feature ideas, integration requests, and reproducible bugs are welcome in GitHub Issues.

If Lians helps your workflow, star the repository so o

Only the beginning is shown; read the rest in the repo

Lians Agent Memory

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Lians Guard

Two layers, one agent loop

One clear result after every agent session

Try it in two minutes

What a fresh coding agent receives

Why this is not another generic memory layer

Project status

Current evidence

Build with Lians

Development