Browser Harness vs mem9.ai

“592 lines to replace Playwright for LLM agents is a compelling trade. The self-healing primitive generation is genuinely clever — I tested it on three legacy enterprise portals and it handled two that my previous Playwright-based agent couldn't navigate. Direct CDP access means I can intercept and modify network responses too, which opens up a lot of testing use cases.”

“The primitive is clean: a drop-in MCP-compatible memory server that swaps file-backed agent memory for a cloud-persistent hybrid search store backed by TiDB. The DX bet is right — complexity lives at the infrastructure layer (TiDB handles distributed storage and indexing), so the agent-side API stays thin. The moment of truth is connecting a second agent to the same server and watching it recall context the first agent wrote; that's the demo that earns the ship. You could not replicate genuine hybrid vector + keyword search with cross-agent consistency in a weekend script — the distributed consistency guarantees alone are a real engineering problem this solves.”

“Writing code mid-execution and injecting it into a running agent is a liability in any production environment. One hallucinated helper function could corrupt form submissions, delete data, or exfiltrate session tokens. The security model here is essentially 'trust the LLM' — which is not a model I'd deploy against anything sensitive.”

“Direct competitors are Zep, Mem0, and whatever LangChain Memory ships next — and mem9 beats them on one specific axis: the TiDB backend means you're not doing vector-only retrieval on structured technical knowledge, where BM25 keyword search materially outperforms cosine similarity. The scenario where this breaks is large teams with conflicting write patterns — there's no obvious memory conflict-resolution story yet, and shared mutable state across agents will produce garbage reads at scale. What kills it in 12 months: OpenAI or Anthropic ships native persistent memory into their API that frameworks adopt overnight — but until that happens, the open-source Apache-2.0 license and TiDB's infrastructure credibility make this the most defensible standalone memory layer I've seen.”

“Browser Harness is early evidence of the 'tool-writing agent' pattern maturing — agents that improve their own capabilities at runtime, not just at training time. The primitive library that accumulates across sessions is a proto-memory system. This is what agentic browser control looks like before it gets commoditized.”

“The thesis is falsifiable: within three years, multi-agent systems working on shared codebases will require a persistent, shared knowledge substrate the same way they require a shared filesystem today — and whoever owns that substrate owns a critical layer of the agent stack. The dependency that has to hold is that agents remain heterogeneous (different vendors, runtimes, frameworks), which keeps a neutral shared memory layer valuable versus each model provider building their own silo. The second-order effect nobody is talking about: if your CI pipeline agents and your local dev agents share the same memory, institutional knowledge stops living in Confluence and starts living in a queryable, semantically indexed store that actually surfaces when relevant — that's a genuine shift in how teams externalize context.”

“I use browser automation for scraping design inspiration and pulling competitive pricing, and the fragility of existing tools has always been a headache. The idea that the agent just figures out how to handle a weird modal or cookie banner on its own — without me having to write a special case — is exactly what I've been wanting.”

“The buyer here is a platform or infrastructure engineer at a company already running multiple AI agents — a narrow, technical buyer who will self-host before paying for a cloud tier that doesn't exist yet. The moat is real (TiDB's distributed infra is not easily replicated and the Apache-2.0 open-core is a proven wedge strategy), but the monetization path is invisible: 'cloud hosted pricing TBD' is not a business model, it's a GitHub repo with ambitions. What would flip this to a ship is a credible hosted tier with pricing that scales on memory operations or agent seats — something that creates a natural land-and-expand motion from the indie dev who self-hosts to the enterprise team that pays for managed reliability.”