core vs rowboat
Self-hosted, always-on "personal AI OS": watches your apps, keeps a persistent memory graph, and acts autonomously within guardrails — a product, not a library for building agents. — versus — Desktop AI coworker (YC S24) that indexes email, meetings and Slack into a living backlinked knowledge graph, then acts on it — email client, browser, meeting notes, background agents, code mode.
The two strongest 'personal AI OS' plays in the catalog: both keep a persistent memory graph and act autonomously within guardrails. core watches your apps from the background; Rowboat ships its own work surfaces — email, browser, meeting notes — and stores the graph as editable local Markdown.
| core | rowboat | |
|---|---|---|
| Stars | 1.9k | 17k |
| Forks | 181 | 1.6k |
| Language | TypeScript | TypeScript |
| License | NOASSERTION | Apache-2.0 |
| Last activity | today | today |
| Topics | agents, memory | agents, memory |
| Curated connections | 6 | 3 |
core — the curator's take
Reach for CORE when you want an event-driven, self-hosted personal assistant that notices things on its own, remembers across sessions via a memory graph, and acts across your apps with per-action approval gates. NOT the pick if you want a framework to embed agents inside your own software (it's a product/OS, not a toolkit), nor if you need to run a multi-agent team/company with org charts and budgets — that's paperclip's lane.
rowboat — the curator's take
The thesis is memory that compounds vs retrieval that starts cold: everything you touch gets indexed into an Obsidian-style backlinked graph stored as plain local Markdown — inspectable, editable, yours — and the work surfaces (email client that drafts replies with full context, isolated browser, local meeting transcriber, event/schedule-triggered background agents) all read from it. Code mode drives Claude Code or Codex with that context. BYO model including Ollama. Use it if you want one desktop app to BE the AI layer over your work life. When NOT: it's maximalist by nature — email + browser + meetings + code in one young app means breadth outruns polish in places, and Google-service setup is a manual OAuth dance. Data stays local; that part they got exactly right.