Practical overview
When it fits
Use it when a browser-based search over text can surface relevant passages even when they use different wording from the query. For very large libraries or ongoing collections, the project points users toward a vector database.
Who it is for
- People searching personal notes or other text collections by topic rather than exact keyword.
- Readers exploring long documents and books for relevant passages or recurring themes.
- Developers interested in building or locally building the web app or Chrome extension.
Documented uses
- Find passages related to a natural-language search in document text.
- Combine semantic matching with full-text search.
- Create and save an index for a custom text collection.
- Use a pre-indexed example to search a large book.
Requirements & limits
- Embedding generation happens before repeated searches and can take time; the README reports one to two minutes for a 660,000-character test on an older CPU.
- WebAssembly supports the compatible models listed by the project; using WebGPU requires a WebGPU-compatible model.
- The Chrome extension includes settings for multilingual use and minimum text-segment length.
- The repository documents local builds using npm, including separate instructions for the extension.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Install and run SemanticFinder from its repository
Start the SemanticFinder application locally from a cloned repository.
Before you start
- A cloned SemanticFinder repository
- npm
Steps
From the repository directory, install dependencies with the command below.
npm installStart the application with the command below.
npm run startOptionally, create a build with the command below; the README says
index.html,main.css, andbundle.jsare placed indist.npm run build
Expected outcome
The application is started with the repository's start script; the optional build produces the listed files in `dist`.
Guide limitations
- The README does not specify browser or runtime compatibility details.
- For larger texts or an entire library of books, the README recommends using a vector database instead.
Build and load the Chrome extension locally
Create a local extension build and load it into Chrome.
Before you start
- A cloned SemanticFinder repository
- npm
- Chrome
Steps
Open a terminal in the repository's
extensiondirectory.Run the command below.
npm installRun the command below for a static build, or the command below for the auto-refreshing development version.
npm run buildnpm run devIn Chrome, open
chrome://extensions, selectLoad Unpacked, and choose thebuildfolder.Pin the extension in Chrome to access it easily.
Expected outcome
The locally built extension is loaded in Chrome and can be accessed from its pinned toolbar icon.
Guide limitations
- The README notes that the extension may not work for everyone and suggests opening an issue if it does not.
- The extension options include a multilingual model choice; the default is English-only.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 16 October 2026
- Original website title
- do-me/SemanticFinder · Official homepage title · retained in its source language

