Unverified50% confidenceSolutionExact time
When reading the DeepSeek Harness source code, it is recommended to first get both the installed version and the source version running and distinguish them by port and debug logs, then start from the plugin registry and event bus, treat the main loop as a scheduler, and finally write a minimal plugin to connect MCP.
1
Sources
50%
Confidence
Long-term
Relevance
11/4/2026
First Seen
Sources
DeepSeek Harness Source Code Deep Dive: Everything Is a Plugin and the Event Bus
bilibili黑帽小新11/4/2026
Related Entities
Related Claims
UnverifiedThe interactive experience of DeepSeek Harness is very close to the DeepSeek web version, but as a locally runnable shell, developers can swap models and connect custom MCP services without modifying the main loop.75% similarUnverifiedDeepSeek Harness is still in the development preview stage, and both version numbers and interfaces may change; when following the source code, the repository's current state should be taken as authoritative.75% similarUnverifiedReading the DeepSeek Harness source code can proceed along three main lines: the plugin system, the main loop, and the event bus.74% similarUnverifiedDeepSeek Harness的编码能力插件安装后可通过`@`提示符引用当前项目下的单个文件或目录72% similarUnverifiedThe new version of DeepSeek Harness supports modifying system prompts while retaining existing KV cache, and adds features such as file upload, sidebar file preview, and bidirectional sub-agent communication.72% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1136369API
curl https://kongchang.com/api/v1/knowledge/claims/1136369MCP
get_claim(id=1136369)