dsh-local-context
无需原生依赖的 DeepSeek Harness 本地 FTS5 知识库：智能截断 Shell 输出、文本索引，以及适合中日韩文字的相关性搜索。
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:akske/dsh-local-context#2b90489ddf0adc18c6bab0190edaa3eef4635f62Local Context 以 dsh-local-context 发布，当前版本为 0.1.0。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
A local knowledge base for DeepSeek Harness (DSH) with zero native dependencies.
Stop compiling C++ and installing Visual Studio just to keep long tool output out of your context window. dsh-local-context saves full command output into a local SQLite FTS5 database using Node's built-in node:sqlite — no native addons, no prebuilt binaries, no build step.
中文文档 · Why · Features · Install · Tools · How it works · Configuration · Development · License
Agent tool results are context poison: a single npm test, git diff, or JSON dump can add thousands of tokens that you keep paying for until the session ends. The usual fix is a context-mode style plugin that extracts what matters into a searchable store.
Most of those plugins depend on native SQLite bindings. On Windows that means Visual Studio Build Tools, Python, a compiler toolchain, and the occasional native build failure that eats an entire afternoon.
This plugin makes the opposite trade: a simpler search stack built only on what already ships inside Node 24 / Electron. You install a folder; there is nothing to compile.
package.json declares none... [省略 N 个字符的输出] ...).ctx_search.LIKE, where a pure trigram index cannot match.full=true for the complete chunk.taskkill /T /F.cat cannot exhaust memory; the command is stopped and what arrived is still stored.title replaces its chunks, so build-fix-build loops do not accumulate stale data.busy_timeout; a broken database never prevents the DSH profile from booting.Requirements: DSH desktop on Windows 10/11, Node 24+ (bundled with current DSH desktop builds), Git Bash recommended for language: "bash".
git clone https://github.com/akske/dsh-local-context.git
Install the folder as a DSH bundle (official path):
plugin_manager(action: "install_bundle", target: "<absolute-path-to>/dsh-local-context")
Run this through the DSH plugin manager if your build exposes local bundle installation, or simply ask your DSH agent to install the bundle at that path. The CLI route also works where the profile's package manager is healthy:
dsh plugin --profile desktop add "<absolute-path-to>/dsh-local-context"
The three tools usually appear immediately. If they do not, restart DSH once.
Verify:
ctx_exec({ command: "echo hello from ctx_exec" })
→ hello from ctx_exec
[exit code: 0]
| Tool | Purpose |
|---|---|
ctx_exec | Run a shell command; truncate long output and archive the full text |
ctx_index | Chunk text into the local knowledge base |
ctx_search | Relevance search across everything stored |
ctx_exec| Parameter | Required | Description |
|---|---|---|
command | yes | Shell command. For Python/Node, write python -c "..." / node -e "..." |
language | no | bash (default, Git Bash), pwsh, cmd |
cwd | no | Working directory; relative paths resolve against the session directory |
timeoutMs | no | 1000–600000, default 120000; timeout kills the process tree |
ctx_exec({ command: "git log --oneline -20" })
ctx_exec({ command: "npm test", timeoutMs: 300000 })
ctx_exec({ command: "python -c 'print(sum(range(10)))'" })
Truncation contract:
N = total - 4000.ctx_search.ctx_exec({ command: "printf 'A%.0s' {1..6000}; printf 'NEEDLE'; printf 'B%.0s' {1..6000}" })
→ AAAAAAAA... (2000 chars)
... [省略 8020 个字符的输出] ...
BBBBBBBB... (2000 chars)
[exit code: 0]
[警告：输出过长已被智能截断，完整原始输出已存入本地知识库。你可以使用 ctx_search 工具搜索关键信息]
ctx_search({ query: "NEEDLE" }) then finds the omitted middle.
ctx_index| Parameter | Required | Description |
|---|---|---|
text | yes | Text to index; up to 1,000,000 characters per call |
title | no | Source title; re-indexing the same title replaces old chunks |
Markdown headings become chunk titles (doc > section), code fences stay intact, and the response reports only counts.
ctx_search| Parameter | Required | Description |
|---|---|---|
query | yes | Search terms; 1–2 character Chinese queries are supported |
full | no | true returns the complete matched chunk instead of a snippet |
limit | no | 1–10, default 3 |
ctx_search({ query: "trigram" })
ctx_search({ query: "开发" }) # short CJK → LIKE fallback
ctx_search({ query: "UNIQUE_TOKEN", full: true }) # complete chunk
ctx_search({ query: "timeout", limit: 5 })
┌────────────────────────────┐
ctx_exec ───► │ shell (bash/pwsh/cmd) │
│ └─ timeout → taskkill /T │
└────────────┬───────────────┘
│ stdout + stderr (≤ 4 MiB)
▼
┌────────────────────────────┐
│ truncate: 2000 + 2000 │──► returned to the model
└────────────┬───────────────┘
│ full raw text (only when truncated)
▼
┌────────────────────────────┐
│ FTS5 chunks (trigram) │◄── ctx_index
│ node:sqlite · WAL │
└────────────┬───────────────┘
▼
┌────────────────────────────┐
│ ctx_search: bm25 → snippets│
│ short query → LIKE fallback│
└────────────────────────────┘
Search strategy is deliberately small:
MATCH with all terms (AND), then with any term (OR).LIKE substring matching.bm25(chunks, 5.0, 1.0); return snippets or full chunks.Everything runs in the DSH Host process; there is no server, socket, or subprocess for the database.
All keys are optional. Configure them in the bundle row in cordis.patch.yml:
| Key | Default | Description |
|---|---|---|
dbPath | $DSH_HOME/local-context/local_context.db (~/.dsh/local-context/local_context.db) | Absolute path to the SQLite file |
bashPath | auto-detect | Explicit bash executable when PATH and common Git installs fail |
pwshPath | auto-detect | Explicit pwsh/powershell executable |
The environment variable DSH_LOCAL_CONTEXT_DB overrides the default path; dbPath wins over the environment variable.
- insert:
- id: local-context
name: dsh-local-context
config:
dbPath: 'D:/data/dsh-local-context.db'
Use an absolute path: a relative dbPath resolves against the DSH process working directory.
-wal / -shm files). Nothing leaves your machine; there is no telemetry.source, origin, timestamp).ctx_exec runs commands with the DSH Host's privileges and no sandbox; never feed it untrusted, concatenated input.npm test # node --test test.js
The suite creates throwaway databases under the OS temp directory and never touches your real knowledge base. It covers truncation boundaries (4999/5000/5001/12000), surrogate pairs, chunking and code fences, exec success/stderr/exit codes, truncation → archive → search, Chinese 2-character queries, re-index replacement, limit/full, malformed FTS queries, the 4 MiB cap, timeout process-tree kill, missing interpreters, and the cmd OEM code-page decoder.
Dependency audit (intentionally trivial): package.json has no dependency fields, and every import is either node:* or a relative path.
index.js plugin entry: apply(), tool registration, result formatting
lib/text.mjs char-safe truncation, snippets, highlighting
lib/chunk.mjs markdown/fence-aware chunker
lib/exec.mjs shell spawning, timeout, process-tree kill, output cap, decoding
lib/db.mjs node:sqlite schema, replace-by-source, bm25/LIKE search
locale/{en,zh}.json plugin-manager display metadata
icon.svg plugin icon
test.js node:test suite (not shipped)
pwsh, and cmd are supported; taskkill is used for timeouts.bash is available and you set an absolute dbPath; the shell auto-detection is Windows-oriented.node:sqlite is available without a flag. Verified with Electron 44.7.0 (Node 24.21.0, SQLite 3.53.4).cmd output is decoded with the Windows OEM code page (936/GBK on Chinese systems) because a piped child cannot switch code pages. Programs that force UTF-8 inside cmd may still garble; prefer bash or pwsh.ctx_index call can briefly block the Host event loop (caps keep this bounded).Inspired by two excellent projects:
This project is an independent rewrite. It vendors no code from either project, depends on neither at runtime, and replaces the native database layer with node:sqlite. Any remaining similarity is at the level of tool names and general architecture.
MIT © 2026 dsh-local-context contributors