Add Lians agent memory

[ebeirne]

What kind of change?

• New agent listing (content/agents/<slug>.json added)
• Correction to an existing entry (URL fix, renamed product, new access method…)
• Removal (product discontinued)
• Code / site change

For new listings

• Product URL: https://github.com/Lians-ai/Lians
• Why it belongs here: Lians is a working Apache-2.0 memory layer with a published MCP server, Python/TypeScript/Go/Java/C SDKs, an official MCP Registry listing, and local credential-free setup that maintainers can verify.
• Your relationship to the product: Maintainer / vendor

Checklist

• npx tsx scripts/validate-content.ts passes locally
• Added a line to content/changelog.json
• All URLs load
• Skills describe real, documented capabilities (not aspirations)
• For vendor submissions: verified: false (maintainers verify & flip)

[vercel]

@etanbuns is attempting to deploy a commit to the assafbar-gmailcom's projects Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Summary

The PR adds Lians as a published agent-memory listing and records its addition in the changelog.

• Adds Lians metadata, capabilities, access methods, and timestamps.
• Adds the corresponding August 13 changelog entry.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
content/agents/lians.json	Adds a schema-compliant Lians listing and now uses a creation timestamp consistent with its changelog date.
content/changelog.json	Adds the Lians entry at the top of the changelog with a date matching the listing timestamp.

_{Reviews (2): Last reviewed commit: "Fix Lians directory creation date" | Re-trigger Greptile}

[assafbar2]

Closing as written, but please do re-submit — the project qualifies, the description does not match it.

The entry describes Lians as durable memory ("memory across chats, sessions, tools, and models", categories memory-state, tags agent-memory / semantic-recall / cross-session-memory). The repo describes something different: "Lians Guard — the current-state and completion guard for AI coding agents… recovers interrupted agent work, rejects stale task state, and blocks done until the current task is ready for human review." Upstream topics are proof-of-done, verification, software-testing, ci-cd. That is a verification tool, not a memory layer, so the categories and tags would be wrong in the catalog.

The traction is fine — presence in the official MCP registry plus PyPI and npm clears the bar on its own. A content-only PR describing it as the completion guard it is would be welcome.