Configuring dsh-plugin-mineru
DeepSeek Harness loads dsh-plugin-mineru in the web profile. Configure the plugin in the DeepSeek Harness GUI settings or in cordis.patch.yml. The required baseURL must point to a MineRU API server, such as http://your-mineru-host:18000.
| Key |
Type |
Default |
Description |
baseURL |
string |
required |
MineRU API address |
apiKeyEnv |
credential-ref |
MINERU_API_KEY |
Environment variable name or credential reference for the API key |
defaultBackend |
enum |
pipeline |
pipeline, vlm-engine, hybrid-engine, vlm-http-client, or hybrid-http-client |
defaultParseMethod |
enum |
auto |
auto, txt, or ocr |
defaultLang |
string |
ch |
Language code for the pipeline backend |
pollIntervalMs |
number |
2000 |
Interval between asynchronous status checks |
pollTimeoutMs |
number |
600000 |
Maximum polling time for mineru_parse_document |
requestTimeoutMs |
number |
60000 |
Timeout for one HTTP request |
maxMdOutputChars |
number |
200000 |
Inline Markdown limit before full content is written to a temporary file |
dsh-plugin-mineru Commands
DeepSeek Harness exposes five tools. mineru_parse_document accepts a local document and handles submission, polling, and Markdown retrieval. mineru_submit_parse_job submits an asynchronous job and immediately returns a task_id. mineru_get_parse_status reports pending, processing, completed, or failed. mineru_get_parse_result retrieves a completed result, returning Markdown inline when possible and storing complete structured JSON at raw_result_path. mineru_health checks server health, version, queue depth, and concurrent capacity.
Requirements for dsh-plugin-mineru
A MineRU instance must be deployed separately and reachable through baseURL. Authentication is optional for a test instance; otherwise apiKeyEnv identifies the API key environment variable or credential reference.
How dsh-plugin-mineru behaves
The client uses HTTP requests to submit files and poll asynchronous jobs. The configured polling and request timeouts govern those operations. The README does not specify a required DeepSeek Harness version or a fixed platform requirement.
Written from the project's own documentation and kept in sync with it. Where the two disagree, the source is authoritative — read the README on GitHub