Can Resurf be vibe coded?
Local-first capture app that saves what you read and resurfaces the useful bits later.
The core mechanic is unglamorous and very buildable: capture the text of pages you spend real time on, embed it, store it locally, then search and resurface it. An agent can get a Chrome extension doing that in a focused implementation, and because the corpus is your own browsing, there is no data moat to lose. Where the DIY version cracks is everything around the loop: cross-device sync, mobile and Safari, capture quality on SPAs and paywalled or auth-gated pages, and the taste of deciding what deserves to come back. Also the honest failure mode of every personal recall tool, which is that you stop opening it after week three. Buildable, yes; pleasant enough that you keep it, less certain.
Jump to the build brief ↓Legacy-calibrated assessment
Checked Aug 2026
low editorial confidence
Tracked separately from the pricing check
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
- A local Chrome extension that captures readable text from pages you dwell on, embeds it on-device, and gives you a semantic search box plus a daily resurface list.
- Save links with full-page snapshots and fast local search.
- A responsive interface with real empty, loading, success, and error states.
The parts a prompt cannot buy
- Sync across devices and browsers, so your phone reading never enters the index
- Capture on anything that is not desktop Chrome: Safari, mobile apps, in-app browsers
- Robust extraction on SPAs, infinite scrolls, PDFs, and anything behind a login wall
- Curation judgment: your version will resurface plenty of pricing pages and airline confirmations
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.
Build, switch, or keep paying
Narrower, with trade-offs
A local Chrome extension that captures readable text from pages you dwell on, embeds it on-device, and gives you a semantic search box plus a daily resurface list.
Use the build brief ↓No checked option yet
Compare the prior art below or build only the workflow you need.
Variable pricing
Because the value only shows up after months of quiet, correct capture, and a homegrown extension that silently stops recording on a Chrome update fails invisibly. Paying for it means the capture layer is somebody's job, the mobile gap is at least on a roadmap, and the ranking has been tuned against more browsing than yours. Personal recall tools are also the classic case where the build is fun and the upkeep is not.
Visit Resurf ↗Why people still pay
Because the value only shows up after months of quiet, correct capture, and a homegrown extension that silently stops recording on a Chrome update fails invisibly. Paying for it means the capture layer is somebody's job, the mobile gap is at least on a roadmap, and the ranking has been tuned against more browsing than yours. Personal recall tools are also the classic case where the build is fun and the upkeep is not.
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 Resurf
Context
Resurf — Local-first capture app that saves what you read and resurfaces the useful bits later.
The core mechanic is unglamorous and very buildable: capture the text of pages you spend real time on, embed it, store it locally, then search and resurface it. An agent can get a Chrome extension doing that in a focused implementation, and because the corpus is your own browsing, there is no data moat to lose. Where the DIY version cracks is everything around the loop: cross-device sync, mobile and Safari, capture quality on SPAs and paywalled or auth-gated pages, and the taste of deciding what deserves to come back. Also the honest failure mode of every personal recall tool, which is that you stop opening it after week three. Buildable, yes; pleasant enough that you keep it, less certain.
This brief describes a focused, single-operator replacement for the part of Resurf 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
A local Chrome extension that captures readable text from pages you dwell on, embeds it on-device, and gives you a semantic search box plus a daily resurface list.
Save links with full-page snapshots and fast local search.
A responsive interface with real empty, loading, success, and error states.
Requirements
Functional
Chrome or any Chromium browser you are willing to load an unpacked extension into.
Node and pnpm for the build.
Disk space for a few hundred MB of page text and vectors.
Data and integrations
Optional OpenAI key if you want better embeddings than the on-device model.
Each of these needs a real account, credential, or quota. Set them up before writing feature code.
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 local-only Chrome extension called "Recall" that indexes pages I actually read and lets me search and resurface them. Empty folder, start from scratch.
Stack, no substitutions: TypeScript, Vite with @crxjs/vite-plugin, Chrome Manifest V3, Dexie for IndexedDB, Preact for UI, @xenova/transformers running all-MiniLM-L6-v2 fully in the extension for embeddings.
In scope:
Content script that waits until a tab has been visible and scrolled for at least 20 seconds, then extracts readable text using Mozilla Readability. Skip if under 300 words.
Store per page: url, canonical url, title, site, extracted text, word count, first seen, last seen, visit count, dwell seconds total. Dedupe on canonical url and update rather than insert.
Chunk text into roughly 500 token pieces, embed each chunk in a background service worker queue, store vectors as Float32Array in Dexie. Never block browsing.
New tab page replacement with: a search box doing cosine similarity over chunks, results grouped by page showing title, site, the best matching snippet, and dates.
A "Resurface" panel on the same page: 5 items per day chosen by a simple score mixing age, dwell time, and revisit count, with buttons for open, snooze 30 days, and never again.
Options page with a blocklist of domains and url patterns, defaulting to blocking localhost, mail, banking, and any url containing "logout" or "checkout".
Export everything to a single JSON file and import it back.
Out of scope, do not build: accounts, any server, cloud sync, telemetry, analytics, payment, sharing, mobile.
Optional: if OPENAI_API_KEY exists in .env, offer it in options as an alternative embedding backend. Default stays on-device. Never commit .env.
Deliver a README with load-unpacked instructions, a note on where the data lives, and one command to wipe the whole index.
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:
Sync across devices and browsers, so your phone reading never enters the index.
Capture on anything that is not desktop Chrome: Safari, mobile apps, in-app browsers.
Robust extraction on SPAs, infinite scrolls, PDFs, and anything behind a login wall.
Curation judgment: your version will resurface plenty of pricing pages and airline confirmations.
Someone else maintaining it against Chrome manifest changes that break extensions on a schedule.
What you still own after launch
Secure credentials, rotate secrets, and handle provider rate limits.
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: low. No reviewed project implementation is linked yet.
Generated by Can It Be Vibe Coded? · Full report: https://www.canitbevibecoded.com/resurf
You still own the product
- Secure credentials, rotate secrets, and handle provider rate limits.
- 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.
Projects built from this idea
No reviewed implementation has been linked for Resurf yet. A submission is evidence for review, not automatic proof that the whole product was replaced.
Built a version of Resurf?Submit the project as evidence for this report.
Before you start
Can Resurf be vibe coded?
Partly, if you narrow it. The core mechanic is unglamorous and very buildable: capture the text of pages you spend real time on, embed it, store it locally, then search and resurface it. An agent can get a Chrome extension doing that in a focused implementation, and because the corpus is your own browsing, there is no data moat to lose. Where the DIY version cracks is everything around the loop: cross-device sync, mobile and Safari, capture quality on SPAs and paywalled or auth-gated pages, and the taste of deciding what deserves to come back. Also the honest failure mode of every personal recall tool, which is that you stop opening it after week three. Buildable, yes; pleasant enough that you keep it, less certain.
What can an AI coding agent reproduce from Resurf?
A local Chrome extension that captures readable text from pages you dwell on, embeds it on-device, and gives you a semantic search box plus a daily resurface list. Save links with full-page snapshots and fast local search. A responsive interface with real empty, loading, success, and error states.
What will a DIY Resurf replacement still be missing?
Sync across devices and browsers, so your phone reading never enters the index; Capture on anything that is not desktop Chrome: Safari, mobile apps, in-app browsers; Robust extraction on SPAs, infinite scrolls, PDFs, and anything behind a login wall; Curation judgment: your version will resurface plenty of pricing pages and airline confirmations; 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 Resurf alternative?
Secure credentials, rotate secrets, and handle provider rate limits. 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.