Can Recall be vibe coded?
Save user-provided sources, summarize them, and build a linked personal knowledge graph
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Recall, save user-provided sources, summarize them, and build a linked personal knowledge graph. The hard boundary is hosted extraction, model routing, browser capture, sync, and knowledge-graph polish, plus capture polish, sync, and content partnerships.
Jump to the build brief ↓Checked Jul 2026
What you pay today, before any DIY hosting
medium editorial confidence
Buildability by layer
Screens, forms, and focused interactions
The repeatable job the product performs
Availability and legality of required data
Uptime, queues, support, and maintenance
Security, compliance, and user confidence
The achievable core
- Save user-provided sources, extract readable text, summarize them, build a linked personal knowledge graph, and export the archive in open formats.
- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- hosted extraction, model routing, browser capture, sync, and knowledge-graph polish
- publisher bypasses
- cross-device mobile capture
- high-quality recommendation graph
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
Why people still pay
People still pay for Recall because people pay when capture works everywhere, reading state syncs instantly, and the archive remains clean without constant parser repairs. The recurring cost buys feed quirks, parsing, paywalls, canonical URLs, deduplication, images, search, sync, browser extensions, and publisher changes, not just the visible interface.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
The brief
Context, requirements, acceptance criteria, non-goals, and the full production standard — as Markdown, ready for any coding agent.
Build brief — a focused alternative to Recall
Context
**Recall** — Save user-provided sources, summarize them, and build a linked personal knowledge graph. It currently costs $10/mo.
The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Recall, save user-provided sources, summarize them, and build a linked personal knowledge graph. The hard boundary is hosted extraction, model routing, browser capture, sync, and knowledge-graph polish, plus capture polish, sync, and content partnerships.
This brief describes a focused, single-operator replacement for the part of Recall that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.
What you are building
Save user-provided sources, extract readable text, summarize them, build a linked personal knowledge graph, and export the archive in open formats.
Build a focused single-user workflow with real persistence, search, and export.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Node.js 22.
Local disk.
Optional browser bookmarklet.
User-supplied RSS feeds.
Non-functional
Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
Security: server-side secrets, validated input, and no credentials in the client bundle.
Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
Portability: the operator can export their data and leave without losing it.
Implementation brief
Build a personal replacement for Recall in an empty repository.
Use Next.js 15, TypeScript, SQLite, Drizzle ORM, Readability.js, and a local background worker; do not offer alternative stacks.
The core loop is: save user-provided sources, extract readable text, summarize them, build a linked personal knowledge graph, and export the archive in open formats.
Make the first run work locally with one documented command.
Store all user data locally by default and make export straightforward.
Put secrets in .env, ship .env.example, and never commit credentials.
Support manual URL save, RSS or Atom subscriptions, OPML import, and a simple bookmarklet.
Fetch politely with a clear user agent, rate limits, conditional requests, and robots-aware behavior.
Extract title, author, date, canonical URL, readable HTML, and selected images.
Provide inbox, unread, archive, favorites, tags, highlights, notes, and full-text search.
Keep the original URL prominent and never attempt to bypass authentication or paywalls.
Export OPML, bookmarks HTML, Markdown, and a complete JSON backup.
Include clear empty, loading, success, and recoverable error states.
Add input validation, safe filenames, and graceful handling of unavailable APIs.
Write focused tests for the core transformation and one end-to-end happy path.
Create a README with setup, architecture, permissions, data location, and backup steps.
Do not add accounts, billing, telemetry, analytics, or a hosted control plane.
Deliberately leave out paywall circumvention.
Deliberately leave out licensed publisher content and recommendation networks.
Deliberately leave out native mobile clients and seamless commercial sync.
Finish by running the tests and listing the exact commands used.
Delivery standard
Inspect the repository first, then write a short implementation plan before writing code.
Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
Add structured logs around every external call and return actionable errors without leaking sensitive details.
Write unit tests for the core logic and one automated test of the main user journey.
Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.
Acceptance criteria
A clean install starts the app using only the README and .env.example.
The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
Tests, type checking, linting, and a production build all pass with no ignored failures.
No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.
Non-goals
Do not build these, and do not claim to have replaced them:
Hosted extraction, model routing, browser capture, sync, and knowledge-graph polish.
Publisher bypasses.
Cross-device mobile capture.
High-quality recommendation graph.
The last 20 percent is sync, migration fidelity, speed, and edge cases.
Connectors, OAuth flows, and vendor API changes require constant upkeep.
What you still own after launch
Run migrations, backups, restores, and dependency updates.
Test the critical journey after every model, API, or hosting change.
Monitor failures and fix the edge cases a first prompt will miss.
Maintain every third-party integration as APIs and OAuth rules change.
Risk
**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.
Editorial confidence in this assessment: medium. No independent one-shot implementation is linked yet.
Prior art
Working open-source software you can read, fork, or borrow from before starting:
[FreshRSS](https://github.com/FreshRSS/FreshRSS) — Mature open-source RSS reader with feeds, filters, and self-hosting support
Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/recall
You still own the product
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.
Open-source prior art
Before you start
Can Recall be vibe coded?
Partly, if you narrow it. The core loop is buildable, but a dependable replacement becomes a substantially larger project. For Recall, save user-provided sources, summarize them, and build a linked personal knowledge graph. The hard boundary is hosted extraction, model routing, browser capture, sync, and knowledge-graph polish, plus capture polish, sync, and content partnerships.
What can an AI coding agent reproduce from Recall?
Save user-provided sources, extract readable text, summarize them, build a linked personal knowledge graph, and export the archive in open formats. Build a focused single-user workflow with real persistence, search, and export. A responsive interface with real empty, loading, success, and error states.
What will a DIY Recall replacement still be missing?
hosted extraction, model routing, browser capture, sync, and knowledge-graph polish; publisher bypasses; cross-device mobile capture; high-quality recommendation graph; The last 20 percent is sync, migration fidelity, speed, and edge cases.; Connectors, OAuth flows, and vendor API changes require constant upkeep.
What do I still own after building a Recall alternative?
Run migrations, backups, restores, and dependency updates. Test the critical journey after every model, API, or hosting change. Monitor failures and fix the edge cases a first prompt will miss. Maintain every third-party integration as APIs and OAuth rules change.