AI Agent Hub
Back to plugins
🧠

dsh-context-milvus

Memory Updated 2026.09.05

Run the following command in DeepSeek Harness:

dsh plugin install bobjia/dsh-context-milvus

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install bobjia/dsh-context-milvus in DeepSeek Harness to install; source code at https://github.com/bobjia/dsh-context-milvus .

About this plugin

Encoding agents inside large codebases hit a familiar wall: string-based grep cannot find semantically related code with different names, multi-round tool calls flood the context with irrelevant text, token costs spike, and model reasoning degrades. dsh-context-milvus plugs a Milvus vector database directly into the DSH Agent process. Code is chunked along function, class, and method boundaries using tree-sitter AST parsing, embedded, and stored in Milvus so that retrieval shifts from needle-in-a-haystack grep to precise recall of relevant snippets, delivering clean context in a single tool call.

On core capabilities, the plugin offers hybrid retrieval that fuses BM25 keyword search with vector semantic search via RRF, incremental indexing tracked with Merkle SHA-256 hashes, cross-file import-resolved call chain tracing (find_callers and trace_call_chain), a three-layer gitignore-style ignore system, and an ADR decision memory layer that records the design rationale behind code changes with semantic search, constraint injection, and consistency checks. Spec document fusion extends unified retrieval to brainstorming design docs as well.

It is built for teams running DeepSeek Harness coding agents on mid-to-large repositories: thousands of files, complex cross-module dependencies, a need to reduce tool-call rounds and token overhead, and a desire for the agent to perform impact analysis and understand historical design decisions before making changes. Supports self-hosted Milvus or Zilliz Cloud, keeping data under your own control.

Use Cases

  • Locate relevant code snippets in large repos with natural-language queries instead of repeated grep and file traversal
  • Run find_callers and trace_call_chain for cross-file import-resolved impact analysis before refactoring
  • Record design decision context via ADR and automatically verify consistency with the implementation after code changes

Best For

  • Dev teams running DeepSeek Harness coding agents on mid-to-large repositories
  • Engineering teams looking to reduce agent tool-call rounds and token overhead
  • Teams with compliance requirements who prefer self-hosted infrastructure for code retrieval