Compare/Core vs Rowboat

AI tool comparison

Core vs Rowboat

Which one should you ship with? Here is the side-by-side panel verdict, pricing read, reviewer split, and community vote comparison.

C

Productivity

Core

An AI OS with a persistent butler agent that works while you sleep

Mixed

50%

Panel ship

Community

Paid

Entry

Core is an open-source "AI operating system" built around a single premise: AI should remove operational friction, not just build-time friction. While most AI tools require you to brief them every session and manually synthesize their outputs, Core ships with Alfred — a persistent, named butler agent that executes scheduled tasks autonomously and surfaces results where you already work. The philosophical distinction is between directive AI (you tell it what to do each time) and ambient AI (it runs your backlog while you focus on other things). Alfred maintains context across sessions, executes routine operations on schedule, and doesn't wait to be invoked. Think scheduled research summaries, automated triage, or recurring data pulls — tasks that currently require either expensive automation platforms or manual check-ins. The project is self-hostable via GitHub and is currently in waitlist mode for the hosted version. It's early-stage, but the architecture — a persistent agent with long-running task support and integrations into existing workflows rather than a separate chat interface — points toward a category of tooling that's been largely missing. Most AI assistants are reactive; Core is explicitly designed to be proactive.

R

Productivity

Rowboat

Local-first AI coworker with persistent knowledge graph, no cloud lock-in

Ship

75%

Panel ship

Community

Free

Entry

Rowboat is a local-first, open-source AI coworker that connects to your email and meeting notes, builds a persistent Obsidian-compatible knowledge graph from them, and uses that context to draft documents, meeting briefs, slide decks, and emails. It works with local models via Ollama or LM Studio, or with hosted APIs, and supports MCP for connecting external tools. The design philosophy is deliberately anti-cloud: all data stays in plain text Markdown files you can read, grep, and version-control. The knowledge graph is transparent — you can open it in Obsidian and see exactly what the AI knows about you. No black-box embeddings in a proprietary vector store, no "trust us with your emails" data agreements. Rowboat implements what Karpathy described as a "long-term memory coworker" — an AI that compounds value over time because it actually knows your history, your projects, and your terminology. TypeScript codebase, Apache 2.0 license, surging on GitHub trending this week.

Decision
Core
Rowboat
Panel verdict
Mixed · 2 ship / 2 skip
Ship · 3 ship / 1 skip
Community
No community votes yet
No community votes yet
Pricing
Open Source / Waitlist
Free / Open Source
Best for
An AI OS with a persistent butler agent that works while you sleep
Local-first AI coworker with persistent knowledge graph, no cloud lock-in
Category
Productivity
Productivity

Reviewer scorecard

Builder
80/100 · ship

The persistent agent with long-running tasks is the right product bet. Most agent frameworks make you rebuild context every session. If Alfred actually maintains state and runs scheduled work reliably, that's solving a real problem. The self-host option with GitHub access is enough to evaluate the architecture.

80/100 · ship

Plain-text persistence + MCP + local model support is the right architecture. It'll survive AI winters and API deprecations. The Obsidian compatibility alone is a killer feature for the PKM crowd that already lives in that ecosystem.

Skeptic
45/100 · skip

Persistent AI agents that run autonomously have a well-documented failure mode: they quietly drift off-task, make irreversible decisions, or rack up API costs with no human in the loop. 'Works while you sleep' sounds great until Alfred posts the wrong thing or deletes the wrong file. The waitlist and vague integration promises suggest this is vapor-forward.

45/100 · skip

The 'knowledge graph from email' promise is where these tools historically fall apart — noisy inboxes produce noisy graphs. And 'local-first' often means 'labor-intensive setup.' The abstraction is right but execution on messy real-world data is hard. Watch the 1-month reviews.

Futurist
80/100 · ship

The ambient computing model — where AI handles operational work continuously rather than responding to prompts — is where the category is heading. Core's framing of 'AI OS' is early, but the architectural intuition is correct. The teams that figure out reliable long-running agent infrastructure in 2026 will be building something foundational.

80/100 · ship

Personal knowledge infrastructure that you own is becoming the moat in AI-augmented work. Rowboat's transparent, portable approach builds durable value. In two years the question won't be which AI assistant you use, but which knowledge graph underlies it.

Creator
45/100 · skip

For creative workflows, I want AI that responds to what I'm making, not one that's silently operating in the background. The waitlist + vague integrations make it hard to evaluate for content use cases. I'd want to see specific creator-focused workflows before recommending this over established automation tools.

80/100 · ship

Drafting meeting briefs and decks from accumulated context is the workflow I've wanted for years. The Obsidian integration means my notes and my AI context stay in sync naturally — no separate import/export dance.

Weekly AI Tool Verdicts

Get the next comparison in your inbox

New AI tools ship daily. We compare them before you waste an afternoon.

Bookmarks

Loading bookmarks...

No bookmarks yet

Bookmark tools to save them for later