Introduction¶

The philosophy of DSH is “everything is a plugin”. The community directory is an independent site with no official affiliation to DeepSeek / Hyperscience, and it should not be interpreted as an official app store.

For users who frequently use the DSH Web UI, when encountering interface anomalies, it is often necessary to confirm if it is a status issue on the DeepSeek official service side. Common practices usually involve opening a separate browser to check status.deepseek.com or setting up a status page of one’s own. Below is a more direct plugin: dsh-deepseek-status, maintained by KekuKase, with a license of MIT. It puts the DeepSeek official service status into the DSH Web UI session header, reducing the need to switch between multiple pages.

What is it¶

dsh-deepseek-status is a DeepSeek Harness (DSH) plugin that displays the DeepSeek official service status (status.deepseek.com) in real-time in the Web UI session header.

No configuration is required after default installation; you can see the status dot in the session header, and clicking it expands the details panel.

Core Features¶

The plugin primarily provides the following capabilities:

• Real-time display of the DeepSeek official service status (status.deepseek.com).
• Display of overall status, last update time, component status, ongoing events/maintenance, recent events, and component availability (uptime%).
• Status dot colors indicate:
• Green = All systems running normally
• Blue = Maintenance
• Yellow = Performance degradation
• Orange = Partial failure
• Red = Critical failure
• Gray = Status unknown
• Click the status dot to expand the details panel.
• The host process polls the official status page and parses Next.js SSR flight data.
• The browser fetches local same-origin routes, avoiding CORS issues.
• When upstream fails, the plugin retains the last successful snapshot and displays the update time, without displaying false normal.
• Under non-web profile, the host row remains pending due to the missing webServer service, with no side effects.

Installation and Activation¶

The plugin requires the following runtime environment and dependencies:

node >=18
@deepseek-ai/schemastery ^3.18.1
@deepseek-ai/dsh-settings >=0.0.1-rc.1

First, install the plugin:

dsh plugin --profile web add dsh-deepseek-status

If using a local checkout, you can install using a local path:

dsh plugin --profile web add ./dsh-deepseek-status

After installation, restart dsh web:

dsh web

After restarting, you can see the status dot in the DSH Web UI session header. Clicking the status dot expands the details panel.

Typical Usage¶

No configuration is required by default.

If you need to adjust the upstream polling interval, you can modify pollIntervalMs. The following items are configurable:

One way is to override the plugin configuration in a profile patch:

# $DSH_HOME/profiles/web/cordis.patch.yml
- id: deepseek-status
  config:
    pollIntervalMs: 120000

Another way is to override it in DSH settings:

# $DSH_HOME/settings.yaml
deepseek-status:
  pollIntervalMs: 120000

You can also modify relevant configurations in the deepseek-status configuration area of the plugin card in the Web settings page.

Applicable Scenarios and Notes¶

This plugin is suitable for those who need to quickly view the DeepSeek official service status within the DSH Web UI. If you don’t want to open a status page separately while handling tasks, you can see the current status directly in the session header.

Points to note during usage:

• No configuration is required by default.
• pollIntervalMs defaults to 60000, which is 60000 milliseconds.
• When upstream fails, the plugin retains the last successful snapshot and shows the update time, it will not display failures as normal.
• Under non-web profile, the host row will remain pending, which is the expected behavior caused by the missing webServer service.
• The plugin runs with the current dsh process permissions; source code and license should be checked before installation.
• License is MIT.

Conclusion¶

dsh-deepseek-status solves a small but specific problem: bringing the DeepSeek official service status into the DSH Web UI session header. It is ready to use with default installation and can adjust polling and timeout configurations as needed.

GitHub Repository:

https://github.com/KekuKase/dsh-deepseek-status