Vibecode Resurf
track this build5 steps, step by step0%KINDA · weekend project
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 weekend, 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.
the project pack4 files · fastest path to a working personal build
You are building a lean indie version of Resurf. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Resurf indie build ## Goal Build the smallest trustworthy replacement for the core Resurf workflow for one developer or a tiny team. ## Scope 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. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use Resurf instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build 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. ## Required capabilities - 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 - Optional OpenAI key if you want better embeddings than the on-device model ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a lean indie version of Resurf. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== README.md ===== # Resurf indie build ## Goal Build the smallest trustworthy replacement for the core Resurf workflow for one developer or a tiny team. ## Scope 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. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use Resurf instead of pretending the gap is solved. ===== AGENTS.md ===== # Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs". ===== BUILD_PLAN.md ===== # Build plan ## Original build 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. ## Required capabilities - 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 - Optional OpenAI key if you want better embeddings than the on-device model ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden. ===== .env.example ===== # Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
You are building a production product version of Resurf. Create the following project files first, then implement the application by following them. Keep the files updated as decisions change. Do not collapse this into a single README or prompt. ===== PRODUCT.md ===== # Resurf product brief ## Problem 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 weekend, 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. ## Product outcome 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. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - 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 - Optional OpenAI key if you want better embeddings than the on-device model ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees. ===== ARCHITECTURE.md ===== # Architecture ## Starting 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it. ===== AGENTS.md ===== # Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone. ===== MILESTONES.md ===== # Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations. ===== OPERATIONS.md ===== # Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Resurf capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
README.md
# Resurf indie build ## Goal Build the smallest trustworthy replacement for the core Resurf workflow for one developer or a tiny team. ## Scope 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. ## Quick start 1. Install the documented dependencies. 2. Copy `.env.example` to `.env`. 3. Run the development command chosen during implementation. 4. Complete the acceptance checks in `BUILD_PLAN.md`. ## Honest limits This build deliberately does not replace: - 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 If those capabilities are essential, use Resurf instead of pretending the gap is solved.
AGENTS.md
# Agent instructions - Optimize for a working, understandable weekend build. - Prefer the fewest moving parts that satisfy the brief. - Do not invent cryptography, security guarantees, APIs, or compliance claims. - Keep secrets out of source control and logs. - Add focused tests for destructive, security-sensitive, and data-loss paths. - Run the project checks before declaring the build complete. - Record any deliberate shortcut in the README under "Tradeoffs".
BUILD_PLAN.md
# Build plan ## Original build 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. ## Required capabilities - 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 - Optional OpenAI key if you want better embeddings than the on-device model ## Delivery order 1. Scaffold the smallest runnable application and document its commands. 2. Implement the primary data model and core workflow. 3. Add validation, safe failure states, and persistence. 4. Cover the critical path with automated tests. 5. Exercise a clean install from the README and fix every missing step. ## Done when - A new user can go from clone to first successful workflow using only the README. - The core workflow works without paid infrastructure unless the brief requires it. - Tests cover the highest-risk behavior. - Known limitations are explicit rather than hidden.
.env.example
# Copy to .env and document every variable when it is introduced. # Never put real credentials in this file. APP_ENV=development # Add only values required by the selected implementation.
PRODUCT.md
# Resurf product brief ## Problem 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 weekend, 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. ## Product outcome 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. ## Target user A serious builder who needs a maintainable product foundation rather than a one-off demo. ## Required capabilities - 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 - Optional OpenAI key if you want better embeddings than the on-device model ## Explicit non-goals for v1 - 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 ## Success criteria - The primary workflow is measurable end to end. - Setup is reproducible in a clean environment. - Failure, recovery, and support paths are documented. - Product claims match what the implementation actually guarantees.
ARCHITECTURE.md
# Architecture ## Starting 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. ## Boundaries Separate the product into replaceable modules for interface, application logic, persistence, external integrations, and operational concerns. Keep domain logic independent from delivery frameworks and vendors. ## Production baseline - Configuration: validated at startup with safe local defaults where possible. - Security: least privilege, input validation, secret redaction, rate limits on abuse-prone paths, and no invented security primitives. - Data: explicit schema and migrations, transactional writes where integrity matters, backup and restore instructions. - Integrations: adapters around third-party providers, idempotent webhook or job processing, bounded retries, and timeouts. - Observability: structured logs with request or operation IDs, an error-tracking hook, and health/readiness checks where a server exists. - Quality: unit tests for domain rules, integration tests at module boundaries, and one end-to-end critical-path test. ## Decision records For each major dependency, document why it was chosen, its failure mode, and how it can be replaced. Do not introduce infrastructure until a requirement justifies it.
AGENTS.md
# Agent instructions - Read `PRODUCT.md` and `ARCHITECTURE.md` before changing code. - Implement milestone by milestone; keep each change reviewable and leave the application runnable. - Treat authentication, payments, encryption, imports, webhooks, and destructive actions as high-risk boundaries when present. - Never invent cryptography or silently weaken a requirement to make a test pass. - Use provider interfaces for external services and deterministic fakes in tests. - Add migrations and rollback or recovery notes for persistent data changes. - Log useful operational context without credentials, tokens, passwords, or personal data. - Update documentation and run all checks before completing a milestone.
MILESTONES.md
# Delivery milestones ## M0 — Decisions and scaffold - Confirm the runtime, persistence model, threat boundaries, and deployment target. - Create a reproducible local environment and continuous checks. ## M1 — Core workflow - Implement the smallest end-to-end product path with validation and tests. - Keep integrations behind interfaces. ## M2 — Trust layer - Add secure failure behavior, recovery paths, audit-relevant events, and data safeguards. - Test abuse cases and destructive operations. ## M3 — Operability - Add structured logs, error reporting hooks, health signals, backup/restore documentation, and deployment configuration. ## M4 — Release gate - Run a clean-install test, critical-path end-to-end test, dependency review, and documented rollback exercise. - Compare the shipped behavior with `PRODUCT.md` and publish remaining limitations.
OPERATIONS.md
# Operations ## Before release - Validate configuration and secrets at startup. - Define backup, restore, and rollback procedures and test them. - Document logs, error tracking, health signals, and alert ownership. - Set dependency update and vulnerability review expectations. ## Incident checklist 1. Contain the issue without destroying evidence or user data. 2. Record the timeline and affected scope. 3. Rotate exposed secrets and revoke compromised sessions or credentials. 4. Restore from a verified source when needed. 5. Document the root cause, remediation, and regression test. ## Launch constraint Do not market omitted Resurf capabilities as implemented. The v1 non-goals in `PRODUCT.md` remain user-visible limitations until they are deliberately delivered.
$ choose a build depth, inspect the files, then open the complete pack in your agent · this prompt is generated from the build plan · improve it via PR
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.
xSync across devices and browsers, so your phone reading never enters the index
xCapture on anything that is not desktop Chrome: Safari, mobile apps, in-app browsers
xRobust extraction on SPAs, infinite scrolls, PDFs, and anything behind a login wall
xCuration judgment: your version will resurface plenty of pricing pages and airline confirmations
xSomeone else maintaining it against Chrome manifest changes that break extensions on a schedule
Nothing worth pointing at. That's why the prompt exists.
share on X ↗"I just replaced Resurf with one prompt"
Vibecode Resurf
Kinda. The core of Resurf is buildable in a weekend with the prompt on this page, but there are real gaps: 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. Read the honest list above before committing.
How much does Resurf cost?
Resurf's pricing is usage-based or varies by plan · Sold as a one-time licence: $49 (launch promo $39), or $99 lifetime; free on iPhone and iPad. Canonical monthly amount is null..
What do I lose by replacing Resurf?
Honestly: 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. If any of those are load-bearing for you, keep paying.
Is there an open-source alternative to Resurf?
No mature open-source alternative worth pointing at, which is exactly why the one-shot prompt on this page exists.