DeepSeek Harness plugin

cc-monitor

Report DeepSeek Harness (DSH) session activity to cc-monitor

Jump to install

Source facts

Repository
BolunHan/cc-monitor
Latest update
Aug 17, 2026
Category
Memory
GitHub stars
0
Format
plugin
Package path
dsh-cc-monitor
Catalog evidence
Upstream dsh.bundle evidence
Evidence path
dsh-cc-monitor/package.json#dsh.bundle
Checked against
0.1.0-rc.8
Upstream check date
2026-08-20

This evidence comes from the upstream catalog. This site has not installed, run, or security-reviewed the plugin.

Install

Start with a prompt that asks an agent to review the GitHub repository and source. Switch to the command if you want to install it yourself.

Copy this prompt into DSH, Codex, or another agent and ask it to review the GitHub repository and source first.

Do not install or run any commands yet. Read this plugin's GitHub repository, README, and relevant source code. Then answer the questions below clearly and directly so I can decide whether it fits my needs:

1. What is this plugin, and what problem does it solve?
2. Who is it for, and what are its typical use cases?
3. How is it used after installation? Include one minimal example.
4. What known limitations or privacy, security, compatibility, or maintenance risks does it have?
5. Give a clear recommendation: recommend, conditionally recommend, or do not recommend, with reasons.

Distinguish statements documented by the repository, inferences from source code, and unknowns. If evidence is insufficient, say so explicitly. Do not guess or simply repeat the README.

GitHub: https://github.com/BolunHan/cc-monitor/tree/HEAD/dsh-cc-monitor
Plugin: cc-monitor
Author: BolunHan

Check the source files

Read the README and other files from this plugin directory before installing.

File explorer2 files
README.mdSource · read only

dsh-cc-monitor

A host-side DSH plugin that reports session activity to a cc-monitor server. It maps DSH session events to the same normalized hook payloads the server already accepts, then POSTs them to /api/event with agent: dsh.

Install

dsh plugin --profile web add link:/path/to/cc-monitor/dsh-cc-monitor

Then make sure the profile's package.json lists dsh-cc-monitor in dsh.profile.bundles (the dsh plugin add command normally handles this for out-of-tree bundles; verify with dsh --profile web --dump-config).

> First npm publish: npm Trusted Publishing can only publish subsequent > versions once the package already exists. Publish the first version once from > a machine with npm login (npm login && npm publish --access public), then > the GitHub Actions trusted-publisher job can publish future versions.

Configuration

Defaults are designed for a local cc-monitor server on 127.0.0.1:9876. Override them with environment variables or a patch entry:

- insert:
    - id: cc-monitor
      name: 'dsh-cc-monitor'
      config:
        # Full override; host/port below are ignored when this is set.
        serverUrl: 'https://192.168.3.25:9876'
        # Or configure host + port separately:
        # host: '192.168.3.25'
        # port: 9876
        uid: 'my-dsh-instance'

If serverUrl is set, port overrides its port. If serverUrl is omitted, host + port are used to build http://<host>:<port>.

SettingEnvironmentDefault
serverUrlCC_MONITOR_URL
hostCC_MONITOR_HOST127.0.0.1
portCC_MONITOR_PORT9876
uidCC_MONITOR_UIDdsh-default
enabledtrue

How it maps

DSH eventcc-monitor eventState
direct user/messageUserPromptSubmitworking
assistant/messagecached, then turn/endStoppending_review
tool/callPreToolUseworking
approval tool callPermissionRequestpending_approval
tool/resultPostToolUseworking
session/disposedSessionEndall_done