dowse

No Windows tool satisfies all three of the following at once:

- Keep a persistent index of file contents, not just file names (Everything can scan contents on demand, but its instant index is centered on names and paths)
- Recognize and index text inside images on ordinary Windows PCs without requiring a Copilot+ device
- One hotkey to summon, full keyboard operation, no perceptible latency

The closest open-source implementation is sist2, but it targets Linux (on Windows it only runs via Docker), treats Chinese text as trigrams, and the project is no longer maintained. dowse is a Windows-native implementation built around these three points.

- Word segmentation via jieba, ranking via BM25 (tantivy engine). No trigrams.
- Automatic file encoding detection (chardetng). GBK-encoded files are decoded correctly before indexing — this matters because a large share of Chinese-language documents on Windows, especially older ones, are still saved in GBK rather than UTF-8, and a search tool that assumes UTF-8 will silently mis-index or garble them.
- Multi-term queries default to AND semantics. Quoted phrase queries match on exact position. Inline operators narrow things down further:path:reports,mtime:>2026-01-01,size:>10mb, uppercaseORbetween groups,-termto exclude.
- OCR runs on the Windows-native engine (Windows.Media.Ocr), fully offline. The zh-Hans language pack also covers mixed Chinese/English text, no extra configuration required.

Design targets; exceeding them is treated as a defect. "Measured" is a from-scratch benchmark ofdowse 0.7.0(i7-13700K / 24 logical cores / 64GB RAM, single machine, single session, 2026-07-12), reusing the byte-identical corpus from the v0.6.1 round-3 benchmark for direct comparability. Full raw output (index/search logs, JSON result files) is kept with the benchmark working directory, outside this repo.

Full-corpus rows measured on the same 10,000-file / 437.66MB text corpus plus 5,100 synthetic 480×200 OCR images (89.8MB) used for the v0.6.1 round-3 numbers above — byte-identical, reused directly rather than regenerated. Indexing is roughly 2x faster and the on-disk text index roughly a third smaller than v0.6.1; both track the new tokenizer (lowercase normalization, alphanumeric-boundary splitting of Latin words) producing a leaner term dictionary. The zero-result query dropped from 135ms (v0.6.1) to a startup-noise-level 31ms, consistent with less index to scan before concluding a term is absent. OCR recognition speed is unchanged this release, since the pipeline was not touched: single-image recognition stays around 170ms, and the sub-30ms readings on repeated identical images are OS-level caching artifacts, not real recognition. The full-corpus text-plus-OCR pass got faster (83s to 46.6s) from the quicker tokenizer and write path, not from faster recognition.

Install the CLI— the library and command-line tool ship as onedowsepackage:

cargo install dowse # once published to crates.io cargo install --path crates/dowse # from a local checkout

git clone https://github.com/ltspace/dowse && cd dowse # CLI cargo run -p dowse -- index D:\docs # build the index cargo run -p dowse -- search 限流 # search cargo run -p dowse -- search "精确短语" # phrase query cargo run -p dowse -- add E:\projects # add another root incrementally (no full rebuild) cargo run -p dowse -- rules show # view index rules (excluded dirs, extra extensions, size cap) # Overlay app (Tauri 2 + Svelte 5) cd crates/dowse-app npm install cargo tauri build # produces the installer under target/release/bundle

Overlay app:Alt+\` to summon,↑↓to select,Enterto open,Ctrl+Enterto reveal in Explorer,Ctrl+Cto copy path,Escto hide. Two nearly invisible dropdowns sit at the right of the search bar — file type filter (Ctrl+P) and sort order (Ctrl+S, relevance / newest / oldest / largest); both stay faint until you select a non-default value. Right-click a result row for a native Explorer-style context menu (open / reveal in folder / copy path / copy name). A pin toggle at the top-right keeps the window open when it loses focus (session-only, resets on restart). With an empty input, the overlay lists your recent searches (last 10, stored locally) —↑↓/Enterto reuse one,Deleteto remove it.Ctrl+, opens the settings panel — general (hotkey rebinding, transparency, autostart, interface language) and index rules (excluded directories, extra text extensions, per-file size cap).

Three tools:search(query, limit,sortby relevance / mtime / size, comma-separatedextfilter,offsetpagination with atotal_hitscount),preview(full snippet + metadata for one hit),index_status(document count, index health, active index rules). The server never touches the index writer — it only reloads the reader before each call, so it can run alongside the overlay app or a livedowse watchsession without write contention.

┌─────────────────────────────────────────┐ │ dowse │ │ library core: tantivy index · jieba │ │ segmentation · encoding detection · │ │ text extraction (txt/md/pdf/code/ │ │ docx/xlsx/pptx) · OCR pipeline │ │ ───────────────────────────────────── │ │ CLI + MCP server (default cli feature) │ └────────────────────┬────────────────────┘ │ library API │ (default-features = false) ┌───────┴────────┐ │ dowse-app │ └────────────────┘

Two crates.dowseis both the search library and the command-line tool: the library core exposes the search API, and the CLI plus the read-only MCP server ride behind the defaultclifeature in a single binary — the CLI for scripting and debugging, the MCP server for AI agents.dowse-app, a Tauri 2 + Svelte 5 resident overlay, is a separate crate that depends ondowseas a library only (default-features = false, so it pulls in neither the CLI nor its dependencies).

The index is stored locally (%LOCALAPPDATA%\dowse`). No network access, no telemetry. You can verify this yourself: watch the process in Resource Monitor or a firewall tool and confirm it opens no outbound connections. Releases also include a SHA-256 checksum for the installer so you can verify the download.

As a kid I had a single Coolpad phone. In the long stretches without internet, I would open the file manager and study the files one by one, trying to figure out what they were and how they fit together, forever lost among files scattered everywhere with no idea what any of them held.

In college I bought a QNAP NAS and discovered Qsirch, a genuinely good thing, except it lived only on the NAS and had no Windows version.

screenpipe got there first, a kind of primitive version of the memory grain from Black Mirror S1E3, The Entire History of You. Very future, very post-modern, close to the ultimate form of local search, but far too heavy for the world as it is now.

The film Her reads like a prophecy: before long, AI will run our personal computers. dowse takes its cue from that and exposes an MCP interface for AI to call, except what it searches is your own files, on your own machine.

If you are a little obsessive, if you like keeping things in order, if you want real control over your own file system, this is for you. Performance and beauty are things I cared about just as much.

The fastest and the most accurate file search toolkit for AI agents

MCP server for Everything (voidtools) file search

An AI-powered MCP server for advanced file system operations, including search, comparison, and security analysis.

Organize files in your Downloads folder using Cursor IDE with customizable rules.

Visualize directory structures with real-time updates, configurable depth, and smart exclusions for efficient project navigation.

A universal file download assistant supporting secure and batch processing of any file type.

A server for programmatic exploration of local files and folders.

Search for files in the local filesystem using a path fragment.

A simple utility to combine multiple files into a single file.