knqiufan/powercontext-dsh
DeepSeek Harness plugin that connects to a PowerContext Server over HTTP for recall, memory, handoff, experien
PowerContext for DeepSeek Harness connects DSH to a running PowerContext Server over HTTP for recall, memory, handoff, experience, and skills. Before each model step it automatically recalls bounded context (POST /v1/context/prepare, injected as untrusted historical evidence) and captures the current user input as a Content Source (POST /v1/sources/content). Named pc_* tools expose agent-safe Memory (pc_search, pc_remember, pc_memory_list/get/revise/retire), Handoff (pc_handoff_activate/prepare/finalize/commit/continue), Experience and Skill generation (pc_experience_generate/get, pc_skill_generate/get), and read-only Review (pc_review_list/get). DSH requests one-time user approval before named mutations run; review mutations stay explicit human /pc review commands; destructive and administrative OpenAPI operations are not model tools. If the Server is unreachable, recall is skipped and the turn continues. The skill project-context documents the same workflow for the model.
Install
powercontext setup dsh --source oceanbase/powercontext --ref master (or dsh plugin --profile web add <path-or-tarball>)Install the PowerContext Server first (uv tool install "powercontext[cli,server] @ git+https://github.com/oceanbase/powercontext.git@master"), then from a PowerContext checkout the plugin lives at integrations/dsh/plugins/powercontext — prefer the CLI so the ref stays aligned: powercontext setup dsh --source oceanbase/powercontext --ref master (or --source /path/to/powercontext for a local checkout). setup dsh calls dsh plugin --profile web add on that plugin directory. If the CLI is unavailable, add the directory yourself: dsh plugin --profile web add /path/to/powercontext/integrations/dsh/plugins/powercontext, or use a GitHub Release tarball (dsh plugin --profile web add ./powercontext-dsh-0.0.4.tgz). Remove with dsh plugin --profile web remove powercontext-dsh.
Compatibility
DeepSeek Harness Web with a running PowerContext Server (two processes — both required; use the same Git ref for Server and plugin). Calls the Server's /v1/... OpenAPI surface over HTTP — no MCP, no embedded storage. Defaults: http://127.0.0.1:8000, no authentication, SQLite under the user data directory. Also integrated into official PowerContext at integrations/dsh/plugins/powercontext; both stay in sync.
Details
- Repo: knqiufan/powercontext-dsh
- Category: Agent Capabilities
- Stars: 11
- Version: Plugin 0.0.4 (GitHub Release tarball); MIT; DSH web
- Last push: 2026-08-26
- First seen: 2026-08-13
Recent updates
The current README documents the /v1/ OpenAPI integration surface, the automatic recall/capture behavior, the pc_* tool table with HTTP mappings, quick start for Server and plugin, doctor checks (powercontext doctor, doctor dsh), and Windows removal caveats.
FAQ
- Does the plugin embed storage?
- No — it connects to a running PowerContext Server over HTTP; it does not embed storage, start the Server, or import the Python package.
- Does it use MCP?
- No — the plugin calls the Server's /v1/... OpenAPI surface over HTTP.
- What happens if the Server is down?
- Recall is skipped and the turn continues; the plugin does not fail the step.
Alternatives
zh667/TokenLedger · ZSeven-W/dsh-noema · csyangwen/dsh-memory-evolve