dsh-docsmint: Manage DocsMint Documents in the DeepSeek Harness Sidebar

What Does It Do?

DocsMint is a DSH plugin for DeepSeek Harness that brings DocsMint workspace documents into a left-sidebar panel and exposes four document tools the model can call. It removes the need to switch between a chat session and a separate document system, letting you search, read, create and update documents without leaving the harness. It works with both DocsMint Cloud and self-hosted OSS deployments over either the REST API or the MCP server, is maintained by HiAi-gg, and is released under Apache-2.0.

Core Features

• Sidebar document panel: browse documents with workspace, category and folder filters plus sorting by updated time, title or created time, and create categories, folders and documents inline.
• Document editing: change a document's title and Markdown body and save it in place, or open the same document in the DocsMint web app.
• Four agent tools: hybrid search, read a single document, create a document, and update a document, returning ids, titles, snippets and scores.
• Dual transport and deployment: connect to Cloud through OAuth (dynamic client registration plus PKCE) or an API key, and connect a self-hosted instance with its API key in API or MCP mode.
• Secure credentials: keys are kept in the Harness credential store, and the panel never persists secrets in browser storage.
• Visible state: the panel shows which tools the agent has and which transport is active, and the tools follow the same operations as the panel.

How to Use This Plugin?

After enabling it in a DSH web profile, open the DocsMint icon in the left sidebar and connect. Choose OAuth for Cloud, or enter an API key for either deployment; then filter and sort to find a document and edit its title and Markdown body directly. To involve the model, simply ask it to search or read and write documents, and the four tools run over the active transport. Configuration fields can pin the API base URL, transport mode and deployment type, and pinning the base URL disables the panel's deployment choice.

How to Troubleshoot This Plugin?

If no sidebar entry appears, confirm the bundle is installed in the profile you launched, inspect the config dump, and restart that profile. If credentials cannot be saved, enable the Harness credential store, since the panel does not persist secrets in browser storage. If Cloud OAuth fails, check the configured endpoint and authorization callback, then reconnect from the panel. If a self-hosted connection fails, verify the instance URL and key permissions; MCP mode requires authenticated Streamable HTTP at the expected path, so use API mode when the instance does not provide it. If documents look unexpected, verify workspace, category and folder, then reset filters. When reporting an issue, include package and Harness versions with a redacted error, and never include API keys or tokens.