AI Agent Hub
Back to plugins
dsh-peak-block preview

dsh-peak-block

admin-security Updated 2026.09.02

Run the following command in DeepSeek Harness:

dsh plugin install better-er/dsh-peak-block

Paste the following prompt into your AI chat to install this plugin:

Run dsh plugin install better-er/dsh-peak-block in your DeepSeek Harness to install the plugin; the source lives at https://github.com/better-er/dsh-peak-block and it takes effect automatically after restarting the DSH web server with no manual file editing required.

About this plugin

DeepSeek's official API gets congested during weekday peak windows (09:00-12:00 and 14:00-18:00 Beijing time), causing slow responses or outright timeouts that disrupt agent workflows relying on stable conversational chains. dsh-peak-block addresses exactly this: it intercepts requests destined for the official provider during peak hours so you get deterministic behavior instead of passive waiting or repeated retries.

The plugin stays deliberately narrow and clean. It matches only the exact provider name deepseek-official, so third-party DeepSeek relays bundled with pi-ai are never affected. On a hit, it either reroutes to a configurable target provider or blocks the request with a clear prompt—your choice via cordis config. Outside peak windows everything passes through untouched. Interception is scoped strictly to the agent/request dialog path; compaction and other internal streams are left alone. The whole thing is a single source file, no build step, configured entirely through cordis.

It is aimed at users running DeepSeek agent workloads on DSH who want predictable behavior during crowded hours, and who prefer a lightweight single-file plugin over a full routing layer.

Screenshots

Use Cases

  • DeepSeek official API times out during weekday peak hours and you want automatic failover to a backup provider so conversations keep flowing
  • Block peak-hour requests with a clear prompt to prevent agents from burning cycles on futile retries
  • Intercept only the exact official provider without touching third-party DeepSeek relays already in pi-ai

Best For

  • Users running DeepSeek agent workloads on DSH who need deterministic behavior during peak hours
  • Developers who prefer a lightweight single-file plugin over a full routing layer
  • DSH admins comfortable with cordis-based declarative config and zero-build deployment