Letta v2.0 vs Liveblocks AI Presence

“The primitive here is clean and nameable: a stateful memory store with a standard protocol interface, backed by a REST API and now an MCP layer so any compliant client gets read/write access to agent memory without custom plumbing. The DX bet is correct — MCP as the integration surface means you're not writing a bespoke connector for every agent framework, and the REST API means you're not MCP-locked either. First 10 minutes with the repo lands well: docker-compose up, server running, endpoints documented. The specific decision that earns the ship is exposing MCP as a first-class interface rather than an afterthought plugin — that's the right abstraction at the right level of the stack.”

“The primitive is clean: a React hook that injects an AI agent into Liveblocks' existing presence layer, giving it a cursor, a name, and a selection state — no new backend surface, no second SDK to wrangle. The DX bet is correct: they put the complexity in the abstraction, not in the integration. The moment of truth is a single `useAIPresence` call and your agent has a visible cursor within minutes. You could not replicate this on a weekend — Liveblocks' CRDT sync layer and multiplexed WebSocket infra are the actual hard part, and this just exposes a new participant type on top of it. The specific decision that earns the ship: they didn't add a new API, they extended the existing presence model — that's the right call architecturally.”

“Direct competitors here are Mem0, Zep, and whatever memory layer your agent framework ships by default — and Letta beats most of them on one axis: it's the only open-source option in this category with a proper MCP interface rather than a proprietary SDK you have to adopt wholesale. The tool breaks when you need cross-agent memory federation at scale or when your memory retrieval needs go beyond what a single server instance can handle — there's no clear story on distributed deployments yet. What kills this in 12 months is OpenAI or Anthropic shipping native persistent memory tooling that MCP clients can just call directly, making a standalone memory server redundant. What keeps it alive is the self-host requirement for enterprise compliance use cases — that's the real wedge, and it's real enough to ship on.”

“The direct competitor here is 'just log what your AI is doing in a sidebar,' which is what most teams ship today. AI Presence beats that because the presence metaphor maps to user mental models already trained by Figma and Google Docs — a cursor is legible in a way a log entry isn't. The scenario where this breaks is any app where the AI agent operates faster than human perception — a cursor flickering across a document at 200 tokens per second is noise, not signal, and Liveblocks hasn't shown throttling primitives in the demo. What kills this in 12 months: the underlying model providers build native multi-agent orchestration UIs and presence becomes a solved layer in the stack, not a differentiator. To be wrong about that, Liveblocks would need to own enough of the collaboration infra that switching costs make their presence layer the default regardless.”

“The thesis is specific and falsifiable: within 3 years, AI agents will be persistent processes with stateful identities rather than stateless request-response handlers, and the memory layer will become load-bearing infrastructure rather than an app-level concern. What has to go right is MCP achieving genuine protocol-level ubiquity — if it stagnates as a niche IDE feature, Letta's integration surface shrinks considerably. The second-order effect that matters: if this wins, memory management becomes a separate discipline from agent logic, and the team that owns the memory server owns the agent's identity and context budget — that's a meaningful power shift away from the LLM provider toward the infrastructure layer. Letta is early on this trend, not on-time, which is both the risk and the opportunity.”

“The thesis here is falsifiable: by 2027, human-AI collaborative interfaces will require agents to express intent spatially, not just textually, because human coordination evolved around physical co-presence cues — gaze, gesture, position. If that's true, AI Presence is infrastructure, not a feature. The dependency is that AI agents remain slow enough relative to human attention that cursor metaphors remain meaningful; if agents complete work in under 500ms, the presence layer has nothing useful to show. The second-order effect nobody is talking about: this normalizes AI agents as social participants in software, not background workers, which shifts how users attribute responsibility and trust in collaborative outputs. Liveblocks is riding the multi-agent coordination trend and they are early — most teams haven't shipped a single agentic collaborator, let alone needed to display one. The future state where this is infrastructure: any SaaS with a collaborative canvas runs AI presence the way they run user avatars today.”

“The buyer for self-hosted Letta is a platform engineering team at a company building agent workflows with compliance constraints — that's a real buyer with real budget, but the sales motion to reach them is expensive and the hosted cloud pricing isn't publicly listed, which is a bad signal for a product that needs bottom-up developer adoption to build pipeline. The moat question is the hard one: the MCP interface is a protocol integration, not proprietary technology, and Mem0 and Zep are iterating fast on the same surface. The specific business problem is that open-source-with-a-cloud-tier requires either strong community gravity pulling users toward the hosted product or a killer enterprise feature set — Letta doesn't yet show evidence of either, and "we have an MCP interface" is a feature any competitor can ship in a sprint.”

“The job-to-be-done is singular and clear: make AI agent activity legible to human collaborators without building a custom observability layer. Onboarding survives the two-minute test if you're already on Liveblocks — the hook drops in and the agent appears; if you're not on Liveblocks, you're onboarding to an entire collaboration platform first, which is a different product decision. The completeness gap is real: this ships the presence primitive but not the interaction surface — users can see the AI cursor but the blog post doesn't address how users interrupt, redirect, or acknowledge agent actions, which means teams still have to build that layer themselves. The product has a clear opinion — agents are collaborators, not tools — and that opinion is the right one. Ship, but with the caveat that this is a primitive, not a complete human-AI collaboration solution, and teams should scope their expectations accordingly.”