Recall vs Comet
Side-by-side trajectory, velocity, and editorial themes.
After Recall 2.0, the second-brain iterates fast on sources, voice, and control
Since April's Recall 2.0 relaunch — agentic chat, an API and MCP, and the Max tier — the product has been in rapid iteration. It has widened what it can ingest (Instagram, LinkedIn, Apple News, text/Markdown), added Listen Mode voice playback, and now Custom Personas that pin how the AI behaves. The consistent thesis is knowledge-first AI: your saved sources come before the open web.
Recall is layering reach and control onto its chat: more sources in, more ways to steer the AI (personas, multi-step actions), and more model choice (Opus 4.8, GPT-5.5). Release notes point toward public profiles, sharing, and a write API as the next expansion beyond personal capture.
Based on the roadmap notes threaded through these releases, expect public Recall profiles and shared collections, plus a write/bulk-ingest API, to be the next headline moves.
Comet bends Opik from eval and tracing toward AI-cost governance.
Comet's feed centers on Opik, its LLM and agent evaluation and observability layer, plus a heavy run of content on controlling AI and Claude Code token spend. Recent posts announce Comet Cost Intelligence, a Test Suites eval workflow, and an Oracle Open Agent Specification integration, interleaved with educational pieces on evaluation-driven development and agent tracing.
Comet is widening Opik from evaluation and observability into cost governance for agentic systems, while hedging framework lock-in through standard agent specs. The AI-spend theme dominates the feed and now has a shipped capability behind it.
Expect more cost-governance and automated-eval features on Opik plus further framework and provider integrations; the volume of cost-tracking content suggests spend control is the near-term wedge into enterprise LLMOps.
See more alternatives to Recall →
See more alternatives to Comet →