DeepSeek Harness Plugin Hub

发布与管理完整 Harness Profiles,发现适合你的插件。

探索

插件目录环境预设文档中心动态

社区

发布插件联系我们报告问题

相关链接

Plugin Hub GitHubDeepSeek Harness 官方项目系统状态隐私说明
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

独立、非官方社区项目,与 DeepSeek 官方无隶属、授权或背书关系。

Intent Formation — DeepSeek Harness 插件(DSH Plugin)
DeepSeek Harness Plugin Hub
ProfilesPlugins分类动态文档登录管理 Profiles
ProfilesPlugins分类动态文档登录
← Plugins
I

dsh-intent-formation

Intent Formation

与会话绑定的意图形成策略和本地状态工具,适用于 DeepSeek Harness。

插件会安装到这里;不确定时保持 web。

npx -y @deepseek-ai/dsh plugin --profile web add github:rrrrrredy/intent-loop#9e9c4650d3dc55dba6e41bec878f8958dbc10d79
README兼容性版本

兼容性与来源证明

Intent Formation 以 dsh-intent-formation 发布,当前版本为 0.3.0-beta.1。Plugin Hub 会校验它的 manifest,并保存精确安装来源,便于复现安装结果。

DSH 兼容范围
*
运行环境
any
发布来源
github
Registry 更新时间
2026/9/7

版本

0.3.0-beta.1beta
2026/9/7

相关插件

正在加载相关插件…

最新版
0.3.0-beta.1
DSH
*
HMR
重启进程
Tree shaking
未声明可安全裁剪
解包体积
未提供
文件数
未提供
Surface
any
许可证
Apache-2.0
发布源
github
GitHub
★ 0
周下载
0
最近提交
2026/9/8
查看源码 ↗
README Badge

点击下方 Badge 复制 Markdown,粘贴到 README 即可。

这是你的 Plugin?认领权益 · 优先安全扫描

验证 package.json 声明的 GitHub 仓库,即可管理这个公开页面。认领后,Hub 会优先安排当前版本的安全扫描,并在通过后公开展示结果。

认领这个 Plugin →
报告问题

相关插件

继续浏览 memory-context 分类下经过校验的插件。

Memory Plugin@openviking/dsh-memory-plugin适用于 DeepSeek Harness 的 OpenViking 记忆与上下文套件Contextdsh-context用于上下文洞察和管理的 DeepSeek Harness 插件,提供上下文仪表板和上下文命令,帮助了解上下文的构成及其演变过程。Weknora@wxg-prc-cpg/dsh-weknora适用于 DeepSeek Harness (dsh) 的 WeKnora 知识检索工具:通过自有知识库进行语义搜索、文档阅读以及 RAG/代理回答。Memsearch Dsh@zilliz/memsearch-dsh适用于 DeepSeek Harness 的 MemSearch 插件:在多个代理之间共享 Markdown 记忆,支持捕获、步骤前上下文注入、记忆召回技能和技能候选审核面板。

README

Intent Formation

Intent Formation helps Codex follow what you want as you see results and change your mind. Clear tasks continue normally. When a choice genuinely changes the next useful action, Codex asks one focused question, shows two or three concrete directions, or makes a tiny sample you can react to. With local state enabled, short sourced records retain the current goal and distinguish fixing the work from changing the goal.

There is no form to fill in and no separate chat app. Talk to Codex as usual.

Development status: main contains the unreleased v0.3 candidate, including an experimental natural-feedback/state connection. Earlier independent studies did not pass the release gates. Public source and green implementation tests do not establish efficacy; see the current goals and release decision.

What it feels like

  • “Translate this paragraph.” → Codex translates it directly.
  • “Design the product so it feels premium.” → If plausible meanings would produce materially different work, Codex asks one useful tradeoff question.
  • “I know this screen is wrong, but I cannot describe why.” → Codex shows a few small alternatives so you can point to what fits.
  • “The button is broken; keep the design.” → Codex treats that as an implementation correction, not a new preference.

The product stays inside the current task. Codex still owns planning, tools, permissions, implementation, testing, and delivery.

Install the simplest version

These instructions target v0.3.0-beta.1. Check Releases first: if that version is not listed, these commands are not yet a usable public installation path. Follow the instructions attached to an available release instead.

Prerequisites: Codex CLI and Node.js 20 or newer on PATH.

Copy these two commands into a terminal:

codex plugin marketplace add rrrrrredy/intent-loop --ref v0.3.0-beta.1
codex plugin add intent-formation@intent-loop

Start a new Codex task. Review the plugin Hook when Codex asks. The core plugin receives no prompt text through its MCP tool and writes no intent records.

This core-only mode supplies interaction guidance without persistent continuity. Give Codex a task in your own words. To retain the evolving goal across processes, enable State below.

Optional local memory and controls

Install the State companion only when you want a small task-local record that can survive compaction or a later process:

codex plugin add intent-formation-state@intent-loop

Start a new task, review the two local Hooks, then type:

/intent start

Once enabled, continue in ordinary language: “Keep the purpose; fix the spacing,” or “I changed my mind; make it for volunteers.” The development Hook supplies existing records and the current turn reference; Codex uses the existing MCP tools to save material changes. You do not need to copy record IDs for normal feedback. This path is under live acceptance testing and is not yet a released capability.

Use /intent show to check what was actually retained and /intent off to stop. The remaining controls are optional explicit overrides:

MessageEffect
/intent remember <one short goal>In standard mode, save one explicit goal with a receipt; constraint:, preference:, success:, and tradeoff: prefixes are optional.
/intent showShow the active task records and their source.
/intent correct <record-id> => <replacement>After show, copy the record ID and replace its current statement; the old record remains auditable.
/intent exportWrite an integrity-checked JSON export and report its opaque export ID and SHA-256.
/intent privatePurge persisted task content; new record text lives only in the current MCP process.
/intent offStop implicit intent intervention and state updates for this task.
/intent forgetPhysically purge this task from plugin-managed state and managed exports.

/intent off is confirmed only when the reviewed State UserPromptSubmit Hook returns an IF-... receipt. Noninteractive codex exec cannot perform Codex's Hook review; do not treat its model-only fallback as an off switch. Release automation uses the bypass flag only after reviewing the exact packaged Hook.

Successful controls return a short receipt such as IF-12AB34CD. No receipt means no success claim.

Exports are stored under <CODEX_HOME>/plugin-data/intent-formation/exports/<export-id>. The plugin does not place an absolute local path into model context.

The reported SHA-256 is the structured content digest, not the hash of the complete formatted file. Import verifies it automatically; see export verification for the exact calculation.

After /intent start, Codex may save short atomic paraphrases of material user goals and feedback; the ordinary-prompt Hook only reads existing state and does not parse or persist the prompt. Complete prompts, transcripts, assistant responses, workspace files, and tool output must not be copied into records. This content-minimization rule relies on the host for semantic writes; personal information deliberately placed in a statement can still remain. This is not a secret vault or general DLP system. On Unix-like systems, managed directories/files use 0700/0600; Windows relies on the current account's inherited filesystem ACLs.

Local storage is not local-only processing: enabled State supplies selected records to Codex as context, where the host and configured model provider may process them. The plugin has no direct upload or telemetry client.

The trusted short-lived Hook refuses private remember, feedback, show, and correction commands: it cannot retain writes or retrieve another process's private memory. Private records can still be managed through the State MCP tools and last only for that MCP process. Private mode never stores a custom task title or workspace hash. Returning to standard mode with /intent start restores the reliable slash-command path.

See the plain-language Chinese guide, privacy policy, and threat model.

DeepSeek Harness

The repository also contains dsh-intent-formation, a thin adapter for the official DeepSeek Harness developer preview. It shares the exact interaction policy and exposes the optional state tools through a session-bound local MCP process. Setting a session to off removes the policy on the next Harness system-prompt assembly, including after adapter restart.

The new Codex UserPromptSubmit continuity connection is not a claim of equivalent natural-feedback behavior in DeepSeek. The adapter's current claim remains compatibility and local tool lifecycle.

dsh plugin --profile headless add github:rrrrrredy/intent-loop#v0.3.0-beta.1

DeepSeek Harness currently requires Node.js ^22.19.0 or >=24.0.0 and pnpm. The adapter is pinned to Harness 0.1.2-rc.1; prerelease API changes may require a new Intent Formation prerelease. See dsh/README.md.

Evidence status

An earlier 80-scenario run is preserved as a development regression. Because the policy was iterated against that corpus, its strong result is not used as release-efficacy evidence.

The development ablation report records which policy and architecture elements were removed, which removals caused real Hook failures, and the observed model boundary. It is also excluded from release-efficacy claims.

The independently sealed v6 holdout was run to completion and returned STOP: clear-task paired latency, wrong-intervention rate, and inference-denial rate missed their fixed thresholds. A post-run audit also found at least eleven scenarios whose final-match checklist contained facts absent from the user-visible turns, so the run is retained only as a failed diagnostic, never as efficacy evidence.

The v7 primary run produced 155 usable conversations out of 160, leaving 75 complete pairs. Four explicit model-capacity failures and one timeout were retained without primary replacement. The available-pair diagnostic is ineligible for release and also retains failed inference-denial and premature-action gates. A separate case audit distinguishes real rule-selection and delivery-scope problems from hindsight grading; original scores remain unchanged.

The prerelease remains blocked while the failure-derived revision is tested and ablated. Publication requires a newly authored, hash-sealed holdout whose every outcome requirement is an exact excerpt from a user-visible turn and whose follow-up does not introduce hidden first-turn delivery obligations, run verbatim in an isolated Codex Home against one clean candidate commit, with explicit model settings, full plugin-tree fingerprints, randomized blind grading, and every predeclared gate passing. DeepSeek support has a separate compatibility and lifecycle gate; a Codex outcome result will not be presented as DeepSeek efficacy.

Platform boundary

Source and packaging checks run on Windows, Ubuntu, and macOS with supported Node versions. The release gate requires all 18 jobs to pass: 9 Codex package combinations, 6 DeepSeek adapter combinations, and a real temporary DeepSeek package/add/compose/boot-help/remove lifecycle on all three operating systems. Native GUI behavior is outside this headless claim.

Uninstall

If State is installed and you want its current task data removed, run /intent forget first and keep the receipt. Close Codex tasks using these plugins, then run:

codex plugin remove intent-formation-state@intent-loop
codex plugin remove intent-formation@intent-loop
codex plugin marketplace remove intent-loop

On Windows, if removal reports a file in use or os error 32, exit the Codex app and retry from a separate terminal. An active MCP process can hold the installed directory open. Do not delete the source checkout or terminate unrelated Node processes.

For DeepSeek Harness:

dsh plugin --profile headless remove dsh-intent-formation

Removing a package does not remove operating-system backups or exports copied outside the managed plugin-data directory.

Users of the older Intent Loop v0.2 beta should read the v0.2 migration note. This release deliberately does not import old state silently.

Develop and verify

cd packages/intent-formation
npm ci
npm test

cd ../..
npm ci
npm test

The core build creates exact, dependency-contained Codex distributions in plugins/intent-formation and plugins/intent-formation-state. The root suite verifies published study hashes, DeepSeek tool generation, credential isolation, real MCP behavior, and the exact package allowlist.

See CONTRIBUTING.md, SECURITY.md, and the release evidence report.

License

Apache License 2.0. You may use, modify, and redistribute the project, including commercially, while retaining the required license and notices. The license includes an explicit patent grant. See LICENSE and the package-specific third-party notices.