Liveblocks AI Presence vs TUI-use

“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.”

“This is the missing piece for automating legacy ops workflows. Half my toolchain is interactive TUI apps that choke every agent pipeline — TUI-use just quietly solves that. The PTY state machine approach is clever and the API is clean.”

“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.”

“Screen-scraping terminal output to infer state is fragile — any change in terminal colors, locale, or version will break your parser. This works fine for demos but I'd want to see battle-hardened error recovery before running it against anything production-critical.”

“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 real unlock here is making 40 years of terminal software suddenly agentic without a single line change from the original developers. TUI-use could quietly become the bridge that lets AI agents inherit the entire unix toolchain ecosystem.”

“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.”

“Not my usual domain but I can see this saving hours for anyone managing servers — having an agent that can actually ssh in and navigate interactive prompts without getting stuck is genuinely useful. The demo videos make it look surprisingly smooth.”