DeepSeek Harness Plugin Hub

Publish and manage complete Harness Profiles. Discover Plugins for your next setup.

Explore

PluginsPresetsDocsNews

Community

Publish a pluginContactReport an issue

Resources

Plugin Hub on GitHubDeepSeek HarnessSystem statusPrivacy notice
© 2026 DeepSeek Harness Plugin HubPowered byPaxTech

Independent and unofficial. Not affiliated with, authorized by, or endorsed by DeepSeek.

Plugin Dew — DSH Plugin for DeepSeek Harness
DeepSeek Harness Plugin Hub
ProfilesPluginsCategoriesNewsDocsSign inManage Profiles
ProfilesPluginsCategoriesNewsDocsSign in
← Plugins
P

dsh-plugin-dew

Plugin Dew

See what your other coding agents are doing from inside DSH: Claude Code, Codex, Cursor and DSH sessions, their state, and their scheduled tasks.

The plugin will be installed here. Keep web if you are unsure.

npx -y @deepseek-ai/dsh plugin --profile web add github:cinderzhan/dsh-plugin-dew#c0628933c35f3230a334746ab42e4ad4ee90839a
READMECompatibilityVersions

Compatibility and provenance

Plugin Dew is published as dsh-plugin-dew and currently resolves to version 0.1.0. The Hub verifies its manifest and preserves the exact installation source for reproducible installs.

DSH compatibility
*
Runtime surfaces
any
Release source
github
Registry updated
8/26/2026

Versions

0.1.0stable
8/26/2026

Related plugins

Loading related plugins…

Latest
0.1.0
DSH
*
HMR
Process restart
Tree shaking
Safe tree shaking not declared
Unpacked size
Unavailable
Files
Unavailable
Surface
any
License
MIT
Source
github
GitHub
★ 0
Weekly downloads
0
Last push
8/26/2026
View source ↗
README badge

Click the badge to copy Markdown for your README.

Do you maintain this Plugin?Claim benefit · Priority security scan

Verify the GitHub repository declared in package.json to manage this listing. After you claim it, Hub will prioritize a security scan of the current version and publish the result when it passes.

Claim this Plugin →
Report an issue

Related plugins

More verified plugins in agents-orchestration.

Headless@deepseek-ai/dsh-headlessThe dsh one-shot bundle: a direct core Agent/Session runner over dsh-base with no Host, HTTP, or browser layerExperimental Agent Team Web Profile@deepseek-ai/dsh-experimental-agent-team-web-profileExperimental Web profile layer for Agent Teams Remote and UI pluginsSubagent Codex@deepseek-ai/dsh-subagent-codexOne-shot Codex subagent provider over the official app-server protocolSubagent Claude Code@deepseek-ai/dsh-subagent-claude-codeOne-shot Claude Code subagent provider over the official Agent SDK

README

dsh-plugin-dew

See what your other coding agents are doing — from inside DSH.

You run Claude Code in one window, Codex in another, maybe Cursor too. DSH can't see any of it. This plugin gives DSH two read-only tools that parse the session logs those agents already write to disk, and normalize everything to one vocabulary: needs you / running / done / idle.

> is anything waiting on me?

3 matching sessions; 11 scanned over the last 8h (needs you 1, running 2, done 8, idle 0).

NEEDS YOU
· Claude Code · web-app (2m ago) — waiting for approval: Bash
RUNNING
· Codex · api-server (18s ago) — Refactoring the auth middleware
· DSH · notebook (44s ago) — running bash

It is a port of the readers behind Dew, a macOS status bar for the same data.

Install

In DSH Desktop: Settings → Plugins, search for dsh-plugin-dew, install.

Or wire it into a profile by hand — add the dependency and list it as a bundle:

// ~/.dsh/profiles/web/package.json
{
  "dependencies": { "dsh-plugin-dew": "^0.1.0" },
  "dsh": { "profile": { "bundles": ["@deepseek-ai/dsh-base", "@deepseek-ai/dsh-web-app", "dsh-plugin-dew"] } }
}

Requires Node 20+. Reading DSH's own compressed transcripts additionally needs a runtime with zlib.zstdDecompressSync (Node 23.8+); without it the other three agents still work.

Tools

agent_sessions

Lists sessions and what each one is doing.

ParameterTypeMeaning
agentsstring[]Restrict to claude_code, codex, cursor, dsh. Omit for all.
statestringOne of the four states, or active (default, everything but idle), or all.
within_hoursintegerLookback. Defaults to 8.
limitintegerCap on returned rows, highest priority first. Defaults to 25.

Good for: "is my Claude Code run finished?", "which agent is blocked on me?", and — before you start editing — "is another agent already working in this directory?"

agent_scheduled_tasks

Lists recurring agent jobs and when each fires next: Codex automations (RRULE) and Claude Code scheduled tasks (cron), evaluated locally.

ParameterTypeMeaning
agentsstring[]Restrict to specific agents.
include_disabledbooleanInclude switched-off tasks. Defaults to false.

What it reads

Everything is read-only. The plugin never writes into another agent's data directory, never touches a keychain or credential store, and makes no network requests.

AgentSessionsScheduled tasksSource
Claude Code✅⚠️~/.claude/projects/**/*.jsonl, ~/.claude/scheduled-tasks/
Codex✅✅~/.codex/sessions/, ~/.codex/automations/
Cursor✅—~/.cursor/projects/<slug>/agent-transcripts/
DSH✅—$DSH_HOME (default ~/.dsh) and the DSH Desktop harness dir

⚠️ Claude Code scheduled tasks are implemented against the documented contract but have never been observed on a real machine — the parser is defensive and returns nothing rather than guessing.

How the states are decided

Each agent is different, and the honest summary is that only some of this is explicit:

  • Codex and DSH write explicit lifecycle events (task_started / task_complete, turn/start / turn/end), so running and done are read, not inferred.
  • Claude Code is inferred from the transcript tail: an assistant row with stop_reason: "tool_use" and no matching tool_result means a tool was requested and has not returned.
  • Cursor has the least to work with — no tool_result rows and no timestamps — so its state rests on the last row plus the file's mtime.

needs_you is always an inference. No agent writes a "waiting for approval" event, so it is derived from a pending tool call that has gone quiet. The threshold is per tool rather than a single number, because an approved long Bash writes nothing to its log while it runs — silences of two to four minutes are normal — and a flat threshold reports every slow command as a permission prompt.

Privacy

agent_sessions returns a one-line summary of each session, which is an excerpt of that conversation, and those summaries go to your model provider like any other tool result. If that is not what you want:

config:
  redactSummaries: true   # report states and projects, no conversation text

Configuration

config:
  agents: []              # limit the scan, e.g. ["claude_code", "codex"]
  defaultWindowHours: 8   # lookback when a call does not specify one
  redactSummaries: false

Development

npm test        # node --test, no build step, no runtime dependencies

The plugin ships plain ESM — there is nothing to compile. @deepseek-ai/dsh-tools and @deepseek-ai/schemastery are peer dependencies supplied by any DSH profile.

License

MIT