Writer vs Recall
Side-by-side trajectory, velocity, and editorial themes.
Writer's feed is agent-recipe and AI-leadership content, not product changelog.
The crawled feed is Writer's marketing blog and podcast: agent build recipes (pipeline reports, SEO agents), executive interviews, and survey-driven pieces on AI adoption and brand. None of it describes a change to the Writer platform.
The content leans into enterprise agentic AI and the 'brand as moat' narrative, positioning Writer as the platform for production agents. But this is demand-gen output, not shipped capability.
We can't forecast product moves from a blog feed; expect continued agent-recipe and AI-leadership content unless the crawl source is pointed at a real changelog.
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.
See more alternatives to Writer →
See more alternatives to Recall →