Tonks40 downloadsChat with a local DeepSeek Harness runtime using notes, attachments, and optional web tools.
English | 简体中文
Quick start · Feature walkthrough · Documentation · Releases
Deepseedian is a desktop Obsidian assistant powered by a locally installed DeepSeek Harness (DSH) runtime. Ask questions with note context, inspect sources and citations, fork conversations, manage vault memory, generate local article catalogs and Bases, and request manual inline completion.
Version 0.7.2 · GitHub Releases · Community listing. The interface is currently primarily Chinese; an English interface is not yet available.
Captured in Deepseedian 0.7.1 on macOS / Obsidian 1.13.7, using dedicated demo notes. The learning card is an actual deepseek-flash response; no private articles are shown. Responses can vary.

| Trace and context | Forks and catalogs |
|---|---|
Inspect real tool calls![]() |
Fork a conversation![]() |
Check outgoing context![]() |
Preview a local catalog![]() |
Click a screenshot for the full image. Follow the feature walkthrough to reproduce these workflows with the included notes.
Installation status, September 26, 2026: the community web listing is public, but our fresh Obsidian client could not find the plugin, and the public plugin registry did not yet contain
deepsidian. Use the GitHub Release installation below for now; it has passed a fresh-vault native test. The 0.7.1 automated community review completed without blocking errors; advisory warnings remain. See the acceptance report.
Requires desktop Obsidian 1.13.7+, Node.js 24+, and DSH 0.1.7-rc.2. Mobile devices are not supported. Install Node.js separately, then run:
npm install -g @deepseek-ai/[email protected]
dsh web
Configure a model provider and its credentials in DSH and test a conversation there. You can then close DSH Web. Deepseedian starts a separate local runtime; it does not install or update Node.js, DSH, or itself.
Download main.js, manifest.json, and styles.css from the release into your vault's .obsidian/plugins/deepsidian/ directory and enable Deepseedian in Community plugins. Keep data.json and runtime/memory directories when updating. The embedded bridge needs no separate download. The plugin ID remains deepsidian for compatibility with existing settings and conversations.
On macOS, Obsidian launched from Finder may have a different PATH from your terminal. If automatic discovery fails, set the full Node.js executable path and DSH package directory in advanced runtime settings. Find them with command -v node and npm root -g; on Windows, use where.exe node.
~/.dsh or a custom directory, and read explicitly attached external files. Chats, runtime logs, sent attachments, and memory are stored under the vault's plugin directory. No client-side telemetry is added. Remote services have their own data policies, including DeepSeek's privacy policy.draft or encrypted are not access controls. Completion exclusions do not restrict chat tools. Publishing or reviewing this plugin does not require uploading personal articles.See the walkthrough for note chat, context inspection, forks, catalogs, and manual completion. The 0.7.2 acceptance report covers numbered forks, upgrade persistence, and release verification.
AI suggestions can be incomplete or factually wrong. Read them before accepting; completion is not a fact-checking tool. The 0.7 validation report records both successful and failed real-provider cases. Windows/Linux CI does not replace native UI testing, and third-party completion plugins, native input methods, and all themes have not been exhaustively tested. Runtime migration and three-file installation are covered by integration tests.
The check command includes the official Obsidian ESLint rules. Existing general JavaScript/TypeScript findings remain visible warnings; Obsidian rules retain their recommended severity. TypeScript 5.9.3 is pinned for the linter’s compiler API compatibility. Local checks do not replace the directory scan.
Use Node.js 24+ and run npm ci, npm run check, and npm run test:integration (requires DSH). Older-runtime migration fixtures are optional and are reported as skipped when absent. npm run package:release produces the three release assets. Live-provider test scripts incur charges and use synthetic fixtures by default; real-article testing requires authorization. Reports and credentials must not be committed.
Source pushes alone do not deliver plugin updates. Increment the version, publish a matching Git tag and GitHub Release with the three assets, and check the community review results. See the release guide.
The README organization takes inspiration from dsh-TUI: language navigation, highlights, preview, and quick start. The projects are independent.
Licensed under MIT. The DeepSeek whale icon's attribution and license are in THIRD-PARTY-NOTICES.txt and included in the release bundle. The runtime uses DeepSeek Harness; sidebar interaction design draws inspiration from Claudian. Deepseedian is an independent community project, not an official Obsidian or DeepSeek product.