DevRecall.

Save now. Find it later.

A useful reference might be a documentation page, a GitHub discussion, or an answer on Stack Overflow. DevRecall captures that page into a local library. The side panel puts saving, browsing, and searching next to the page you're reading.

The basic flow

The saved page comes first.

1. 01

   Capture

   Extract a page's content and store it locally in IndexedDB.

2. 02

   Enrich

   Optionally add an AI summary, topics, and embeddings with your own API key.

3. 03

   Retrieve

   Search by keyword or combine keyword and semantic results in the side panel.

Saving does not depend on an AI request succeeding. That separation matters: a slow or unavailable provider should not cost you the page you meant to keep.

Two ways to remember a page.

Sometimes you remember the exact function name. Sometimes you only remember what the page explained. BM25 handles the keyword side; embeddings provide similarity search. Reciprocal rank fusion combines the rankings, and results are deduplicated by page.

Useful without a key.

Local saving and keyword search work without an API key. Optional AI features use a key supplied in settings. If an embedding request fails, retrieval falls back to keyword results instead of leaving the library unsearchable.

The library and API key live in the browser profile. There's no separate account or sync service. Using AI features can send page content and queries to OpenAI; users can export or delete their saved data from settings.

Checking the edges.

The Vitest suite covers retrieval modes, cache invalidation, and capture behavior. These are the places where changes can quietly affect what appears in a search result or whether a saved page is up to date.

DevRecall is available from the source repository and GitHub releases. The README explains building the extension and loading it unpacked in Chrome.