Configuration

The provider exposes the web-search-local settings section, persisted to $DSH_HOME/settings.yaml (hot-reloaded, so a change reaches the next search with no restart):

Field	Default	Meaning
`engine`	`auto`	Web backend: `auto` (metasearch: DuckDuckGo + Bing + Wikipedia), `duckduckgo`, or `searxng` (= metasearch, kept for 0.1.x compatibility).
`corpusDirs`	`[]`	Directories to index (absolute or `~`). Only used by the `local` search provider. Empty returns an informed empty result.
`include`	built-in text/code set	Extra extensions to index (with or without a leading dot).
`exclude`	built-in (`node_modules`, `.git`, `*.min.js`, lockfiles, more)	Extra dir names, file names, or dot-suffixes to skip.
`indexDir`	`/web-search-local`	Where `index.db` or `index.fallback.json` and `manifest.json` live.
`maxResults`	`20`	Per-query source cap (the seam re-enforces the tool's bound).
`snippetLength`	`160`	Approximate snippet length.
`autoReindex`	`true`	Re-scan the corpus on each search (bounded by an internal interval). `false` = build on change only.
`maxFileSizeBytes`	`5000000`	Skip files larger than this.

Two ways to configure:

YAML (primary): edit the web-search-local section in $DSH_HOME/settings.yaml (the same file the Settings UI writes). Example:
```
web-search-local:
  engine: auto
  corpusDirs:
    - D:\docs
    - ~/notes
```
UI card: when the deployment renders third-party plugin cards, a card appears under Settings -> Plugins for web-search-local (engine, corpus dirs, max results, snippet length, index dir, auto-reindex, then Save). It is optional: when the deployment does not render cards, the YAML path remains fully functional.

@djdowbnac/dsh-web-search-local

インストール

ドキュメント

Configuration