Project Scope

Wenlan is for serious AI work where decisions, lessons, gotchas, project constraints, and handoffs need to survive beyond one chat.

The product shape is narrow on purpose: one local daemon, shared memory across MCP clients, source-backed pages, review before trust, and readable local artifacts.

Wenlan does not try to own habits, calendars, journaling, personal planning, or a full life-management system.

Those domains can produce useful memories, but Wenlan's scope is the AI work artifact: what an agent needs to continue work correctly.

Wenlan is not trying to bundle dozens of agents, research loops, and productivity workflows. It is the memory layer those workflows can use.

That tradeoff keeps the product easier to understand: capture, recall, handoff, distill, inspect, and continue.

Wenlan exposes a local daemon and MCP connector, but it is not positioned as backend infrastructure for other apps to add cloud memory features.

The intended user is someone using AI tools daily who wants local, inspectable, shared work context.

If a conversation is disposable, Wenlan may add more ceremony than value. The product starts paying off when work crosses sessions, tools, people, or weeks.

A simple test: if the next agent should know it without you explaining it again, it probably belongs in Wenlan.