ninjasln-labs/dsh-knowledge-sqlite

Cross-session knowledge behind a knowledge service seam, using SQLite FTS5 trigram search so Chinese substrings actually match.

Gives the harness a durable cross-session knowledge store with model-facing tools rather than a chat transcript search. Write indexes immediately with no model call and upserts by a dedupe key derived from workspace, scope and key; search does trigram OR with BM25 ranking and one small expansion-model call per query (cached per normalized query, falling back to pure lexical with a degraded marker instead of a tool error when it times out); update is a correction path that preserves id, provenance and stamps; list pages with audit flags; delete tombstones. Two scopes keep it honest: session-scope scratch memory visible only to its own session, and workspace identity taken from the caller's canonical working directory so cross-workspace calls never see content. Events fire on write, update and delete.

Memory ★ 0
View on GitHub ↗

Install

dsh plugin add dsh-knowledge-sqlite

The dsh CLI line. A profile row and a configuration section are also documented for people mounting it by hand, and storage is a single SQLite file with the items table plus two FTS5 trigram tables — one content-only, one joining the enrichment columns.

Compatibility

Two things the page has to say out loud. First, the Chinese README is the authoritative version and the English text may lag it. Second, this implements a community proposal (V1.11), not an official harness feature, and the README says so where it describes the seam contract. Retrieval numbers are the project's own evaluation suite rather than a vendor claim: unicode61 baseline cannot match Chinese substrings at all (0%), pure trigram lexical reaches 7% with 65% on the human set, the default L1 query expansion reaches 21-64%, and opt-in L2 write-time enrichment reaches 50% with 88% on the human set; the stated acceptance gates were passed by the live prototype and reproduced by this bundle's SQLite layer. Writes and deletes are ask-gated through the tools approval seam, so a headless deployment with approval set to never will auto-deny them and must be told so explicitly.

Details

Alternatives

ICCuse/dsh-knowledge · CodfishYao/dsh-knowledge-base-local · imaused/dsh-kb-lite

More plugins in Memory

Browse more in Memory

Guides for Memory plugins