dsh-omp-retry
适用于 DeepSeek Harness 的 OMP 风格重试策略：429 速率限制和思考块绑定拒绝
插件会安装到这里；不确定时保持 web。
npx -y @deepseek-ai/dsh plugin --profile web add github:Rinai-R/dsh-omp-retry#8a3b6c1c6458b30c2d03a700c6950ddefe0daebaOmp Retry 以 dsh-omp-retry 发布，当前版本为 0.2.2。Plugin Hub 会校验它的 manifest，并保存精确安装来源，便于复现安装结果。
OMP-style retry policies for two DeepSeek Harness failures that the built-in executor leaves terminal:
Retry-After up to five minutes.
DSH's default policy is five retries from 500 ms to 10 s, so a TPM/RPM window
can still be active when the budget is gone.thinking block carries a
signature bound to the conversation it was minted in. Proxies and gateways
that fan out to several upstream channels (or rotate conversation identity)
reject it with 400 ... Invalid signatureinthinking block. The block is bound to a different conversation; re-sending the same history usually
succeeds because the next attempt lands on an upstream that accepts it. DSH
classifies the 400 as INVALID_REQUEST and never retries it, so the whole
turn ends.This bundle adds both policies without forking DSH. It prepends one
agent/request-error listener ahead of dsh-llm-retry and owns only those two
failures; every other code stays with the built-in executor, whose own policy
remains the fallback when this bundle is absent.
Rate limits:
max(30 s, provider Retry-After).dsh-llm-retry: one durable policy key per resolved
provider retryPolicy.Thinking-block binding rejections:
retryPolicy budget, so a
provider left at its default still gets the binding retries.Invalid signatureinthinking block or
bound to a different conversation), not on the failure code, so the policy
survives code remapping by a gateway.Both:
llm/retry / llm/retry-started events,
so the normal retry UI and session history still work.SERVER, TIMEOUT, TRANSPORT, EMPTY_RESPONSE, CONTEXT_WINDOW_EXCEEDED,
QUOTA, and AUTH are never retried by this plugin.dsh plugin --profile desktop add github:Rinai-R/dsh-omp-retry
Use your profile name instead of desktop for a web or custom profile, then
restart DSH. The bundle inserts the omp-rate-limit-retry row itself.
The defaults are maxRetries: 10, floorMs: 30000, and maxDelayMs: 300000
for rate limits and maxRetries: 5, initialDelayMs: 500, maxDelayMs: 8000,
jitterRatio: 0.25 for binding rejections. Override the row in the profile's
cordis.patch.yml:
- id: omp-rate-limit-retry
config:
maxRetries: 10
floorMs: 30000
maxDelayMs: 300000
thinkingBlock:
maxRetries: 5
initialDelayMs: 500
maxDelayMs: 8000
jitterRatio: 0.25
maxRetries: 0 disables the corresponding policy. Malformed values fail the
plugin load with a message naming the offending key instead of silently
disabling retries.
For fast non-429 retries, keep the provider policy close to OMP's local backoff:
retryPolicy:
mode: normal
maxRetries: 10
retryableCodes:
- EMPTY_RESPONSE
- RATE_LIMIT
- SERVER
- TIMEOUT
- TRANSPORT
backoff:
initialDelayMs: 500
maxDelayMs: 8000
jitterRatio: 0.25
Keeping RATE_LIMIT in the list is a fallback for when this bundle is removed;
while the bundle is active it takes 429s first.
Verified against DSH Desktop 0.2.1-rc.5. The plugin relies on:
agent/request-error waterfall,llm-retry session projection (llmRetry),llm/retry event shape used by the built-in retry executor.If a future DSH changes those contracts, the plugin may need an update; it fails closed by delegating to the next listener.
The plugin is written in TypeScript under src/; dist/ is the build output
and is committed so github: installs load without a build step.
npm install
npm run build
npm test
npm test builds first, then runs the node:test suite against dist/. After
changing src/, rebuild and commit dist/ — CI fails when the two drift.
anthropic-beta: thinking-binding-controls-2026-08-01 with
thinking.block_binding.prefix_mismatch_behavior: "drop_block", or drop the
stale block before the request leaves the client.Retry-After above maxDelayMs is not waited out.MIT