Strengths
Mosaic targets a genuine problem in agent-heavy engineering teams: useful investigation history often disappears inside private Claude Code, Codex, Cursor and other sessions. The install path is unusually concrete. Mosaic documents a macOS background service, a local read-only replica at `~/.mosaic`, health/repair commands, selective backup scope, session handoff and supported-agent guidance. It explicitly says the installer does not modify coding agents, hooks, MCP servers or editor extensions and that the product does not collect product telemetry. 2
The current web product goes beyond archival memory. It presents live multiplayer terminals, persistent sessions that teammates can resume, agent-to-agent routing and research sandboxes for multi-agent simulations. YC's S26 profile independently confirms the company identity, two-person team and shared-memory/multiplayer direction; its launch material reports roughly 2,000 installs and 37 organizations syncing, but those are company-reported adoption figures rather than independently audited usage. 1 3
An exact September 2026 Wavect review reaches a similar conclusion: the context problem is real, but synchronized transcripts should not automatically be treated as trustworthy organizational memory. Provenance, stale-context handling, secret redaction, tenant/repository scope, deletion and selective retrieval remain core buyer questions. 4
Weaknesses
Mosaic is a 2026 startup with a two-person team, and the product sits directly in a high-trust layer of the development workflow. Public documentation is strong on installation and session synchronization, but much thinner on public numeric pricing, enterprise retention, fine-grained authorization, secret-redaction guarantees, audit/export behavior and large-organization reliability. The current visible install path is also macOS-oriented. 2 3