dsh-chat-digest

dsh-chat-digest

中文 ｜ DeepSeek Harness plugin (profile bundle)

What you have to do is buried in group chats. This plugin keeps a panel of it, and an agent reads the chats for you.

It owns a panel, one resident main-agent session, and the HTTP contract between them. On a schedule — or when you click Fetch — the session reads your chat logs, picks out what you must do, what you can apply for, and what is worth knowing, and rewrites the panel items. Each item can link straight to the original file or image. The core needs no collector; an optional WeChat/QQ pipeline ships with the package. You can also place exports in a private inbox or feed items over HTTP.

Quick start (a fresh install)

Three steps, no pipeline required — the plugin has a default data contract: put chat exports in inbox\ under the agent workspace and the resident session reads them.

1. Install and restart (see Install below). Drop your chat exports into the inbox — plain text, Markdown or JSON (%USERPROFILE%\.dsh\dsh-chat-digest\inbox\ by default; the exact path is state.inbox in GET /chat-feed/api/state). examples/inbox/sample.txt is a tiny sample you can copy in.
2. Click Fetch once. The resident session reads the inbox and adds items to the panel, each linking to its source file.

Want your own wording or your own collector? Copy examples/local/ into a directory of your own, point config.localDir at it, and edit the "where the data comes from" section.

What it looks like

One item as the panel renders it (illustrative):

一、待办
  · 10/08 前提交报名表 · 创新实践项目
      这是什么：面向大一的项目制课程，秋季学期开课
      怎么做：填表 → 导师签字 → 交教务
      注意：20 个名额，先到先得
      → 附件  报名表.docx          （点一下用系统默认应用打开）

二、机会与招募
  · 9/30 截止：校园开放数据挑战赛（可自由报名）
三、有用信息
  · 图书馆研讨间预约 9/28 开放（官方）

Two resident sessions stand behind the panel, one per configured route. Clicking Fetch opens a small menu of those routes; picking one probes its gateway before running — if it does not answer, the round is not triggered and the collection cursor does not move.

How it works

schedule (a set time each day) or the Fetch button
  → pick a route; probe its gateway                       (before spending a model step)
  → wake / reuse the resident main-agent session for that route
  → the session runs the pipeline *you* gave it and reads your chats
  → it posts the items back:  /chat-feed/api/items
  → the panel is rebuilt; attachments become file: / img: links
  → a turn/end counter closes the round; the collection cursor advances

The plugin never parses your chats itself, and it never picks a model outside the routes you configure. What it does own: the panel, the resident session, the round bookkeeping (busy accounting, one automatic retry when a turn ends abnormally), context rotation at a per-route threshold, and the file endpoints.

Requirements

Need	Why	Without it
DSH >= 0.1.5-rc.1	host	—
Node >= 22.5	the loader and the browser half	—
Windows	files are opened through cmd /c start; paths are joined with \	the panel and the API still work; file: links fall back to download
A model route configured in DSH	the resident session runs on it	the panel and manual write-back work; no round can run
wxRoot — your WeChat attachment root	resolving file: / img: links	only <agentCwd>\output is allowed
An ingestion pipeline of your own	reading and distilling the chats	the panel is usable but nothing fills it by itself

Install

dsh plugin --profile web add dsh-chat-digest

web is the profile behind the DSH web UI — substitute your own profile name if you renamed it. Installing already adds the package to the profile's dsh.profile.bundles; do not add it by hand as well, or the loader fails with duplicate loader entry id. Then restart dsh web.

A local checkout works the same way:

dsh plugin --profile web add link:/path/to/dsh-chat-digest

Why the restart: the host half is evaluated once, at mount time. lib/ui.js and lib/right.js are served over HTTP by the package itself (Cache-Control: no-store), so a page refresh is enough for those.

Verify it works

• GET /chat-feed/api/state — one JSON with every self-reporting field: the items, the panel source, the route slots, the collection cursor, the context window and limit, the last error.
• POST /chat-feed/api/collect with {"dry": true} — builds the round prompt and returns it without running anything, so you can read exactly what the agent will be told.
• Click Fetch: the button goes 探测中… → 采集中… and the panel opens. If the gateway does not answer it flashes red, and neither the cursor nor the collection time changes.
• On disk: state.json (items, cursor, route slots) and panel.json inside the private profile.

A fresh install stays empty until you feed items in or run a round. That is expected: the pipeline is yours.

Configuration

Everything is optional and lives in the row's config — either in the package's cordis.patch.yml or, better, in your own profile patch ($DSH_HOME/profiles/<name>/cordis.patch.yml), which wins:

- id: dsh-chat-digest
  config:
    localDir: 'C:\path\to\your\private-profile'       # private data and resident session workspace
    wxRoot: 'C:\path\to\wechat\attachments'
    routes:
      - id: 'free'
        label: 'Free'
        provider: 'your-provider'
        model: 'your-model'
        probeUrl: 'https://your-gateway/v1/models'
        ctxRatio: 0.75
      - id: 'paid'
        label: 'Paid'
        provider: 'your-other-provider'
        model: 'your-other-model'
        default: true

Key	Default	Meaning
bodyPath	<package>/lib/host-body.txt	the authoritative host body; DSH_CHAT_FEED_BODY overrides it
stateDir	localDir (the private profile)	where state.json and panel.json live
agentCwd	localDir (the private profile)	must resolve to the same physical directory as localDir; normally omit it
dshHome	$DSH_HOME, else %USERPROFILE%\.dsh	used to read session titles
agentPreset	empty	agent preset to create the sessions with
routes	one generic route	[{ id, label, provider?, model?, effort?, probeUrl?, ctxRatio?, default?, hint? }]. Two routes is the intended shape; with none configured there is a single route that pins no provider or model, so the session inherits the host default
localDir	<DSH_HOME>/dsh-chat-digest	the physical private profile directory — see below
inboxDir	<agentCwd>\inbox	the default data source the built-in prompts tell the agent to read. {inbox} in a local/round.md expands to it, and it is in fileRoots by default
wxRoot	none — set it	WeChat attachment root — only needed for attachments outside the inbox and <agentCwd>\output
fileRoots	[wxRoot, <agentCwd>\output]	roots allowed for byte serving and "open in the default app" (rejects .., absolute paths outside the roots, and UNC)

Your private profile (local, never uploaded, survives updates)

Your private things (prompt overrides, private config, products, knowledge base, archive, panel state) live in the plugin's own profile directory:

<DSH_HOME>/dsh-chat-digest/           default = %USERPROFILE%\.dsh\dsh-chat-digest
    pipeline.yaml  pipeline.json      wxid / database keys / group names / paths
    output/  knowledge/  archive/     products / knowledge base / archive
    docs/  state.json  panel.json  profile.md

• <package>/local, <package>/profile, agent/output and agent/docs/{knowledge,archive} are compatibility junctions. The session cwd and all new writes use the physical private directory.
• Why not inside the package: dsh plugin add <package>@<version> rebuilds the whole package directory, so private files kept there are lost on every update.
• Why not somewhere else: under ~/.dsh the * rule in ~/.dsh/.gitignore ignores it, and the repository .gitignore plus the package files whitelist exclude local/profile/output/ knowledge/archive/state — three layers, so it is never uploaded.
• Fresh installs work: mount creates an empty private directory and compatibility junctions; it never copies the sample chat into the inbox automatically.

Your own prompts

The wake prompt and the per-round instruction ship inside the package (general, full text):

Where	What
<package>/prompt/prompt.md	the prompt that wakes the main agent
<package>/prompt/round.md	the per-round instruction ({date}, {mode}, {since}, {agent}, {pkg}, {profile}, {py}, {work} are substituted)

To use your own wording, drop a prompt.md / round.md of the same name into your private profile; it wins. Lookup order = private profile → <package>/prompt/ → built-in generic.

localDir resolves in this order: config.localDir → $DSH_CHAT_FEED_LOCAL → <DSH_HOME>/dsh-chat-digest. The directory is .gitignored and excluded from the published files whitelist, so private prompts and paths never reach the repository or the npm tarball.

What it writes, and what it costs

• Core state lives under stateDir: state.json (atomic write, a .bak copy, and a .corrupt-<ts> quarantine when parsing fails) and panel.json. The optional pipeline writes products under the private profile's output/; the package directory stays read-only. A bad state file is never deleted.
• Legacy state locations (%LOCALAPPDATA%\chat-feed\, <旧临时目录>\, %TEMP%\dsh-chat-digest\) are read once as migration sources, then left in place.
• A round uses the configured model route and any optional collector you enable. The plugin sends no telemetry.
• Rotation is per route, according to that route's ctxRatio setting.
• Model credentials come from DSH. Optional database keys belong only in the private profile.

Uninstall

dsh plugin --profile web remove dsh-chat-digest

Then restart. Delete <DSH_HOME>\dsh-chat-digest\ if you also want the panel data gone — deliberately a manual step, since it is the only copy.

Troubleshooting

Symptom	Likely cause
The panel stays empty	nothing has fed it. POST items to /chat-feed/api/items, or set localDir + a pipeline and run a round
Fetch flashes red	the picked route's probeUrl did not answer. The cursor and the collection time are untouched by design
A round never finishes	the resident session is still working, or a turn ended abnormally — the plugin retries once and says so in state.note
The panel fell back to the built-in three sections	panel.json is missing or invalid; GET /chat-feed/api/panel reports which. Nothing is overwritten
Items point at files that will not open	the path is outside fileRoots. Add the root, or set wxRoot
Items are missing after an upgrade	the state migration reads the old locations; state.note records the source path it used

What it does not do

• The optional ingestion pipeline needs extra software and your own data. Its scripts ship in pipeline/; their Python packages are listed in pipeline/requirements.txt. Configure python and external_dir in the private pipeline.yaml for the interpreter, WeChat decryptor, and QQ export tool; update these local paths after moving machines. The core panel and inbox path have no npm dependencies.
• It does not ship model credentials, and it does not choose models outside your routes.
• It does not do off-site backup. Copy stateDir yourself if you want one.
• It has only been verified on Windows.

Development

Layout:

Path	What is in it
lib/plugin.js	the loader: reads the body, evaluates it as new Function('CFG', text)(cfg), calls apply
lib/host-body.txt	the authoritative host half: routes, session slots, panel, scheduled rounds, rotation
lib/ui.js	the browser half: sidebar entry, the Fetch dropdown, the panel shell
lib/right.js	the panel's item list and rich text (file: / img: links)
docs/	INDEX.md, STATUS.md (change history — grep it), COLD-START-ENGINEERING.md, ARCHITECTURE.md, audit-2026-09-20/
test/	23 host probes + 6 pipeline probes
tools/	check_host_body.py (self-check) plus one-off diagnostics

npm run check                            # syntax check the three runtime JS files
npm run check:body                       # host body self-check (must print FAILS: 0)
npm run test:host                        # 23 host probes
npm run test:pipeline                    # 6 pipeline probes

Two rules this repository holds itself to:

1. After editing lib/host-body.txt you must restart dsh web, and add the new fragment to tools/check_host_body.py's list.
2. Probes must not modify the repository they check: the pipeline probe runs its fixtures in a temp directory, and the self-check writes its scratch copy to the system temp dir. Before asserting "the repo is clean", look at who wrote the changes in git status --porcelain.

prepack runs check and test:host, so a package that fails either cannot be published. CI runs the same two commands on Ubuntu and Windows with Node 24. The Python probes are local-only on purpose: they are the author's own instruments, not a release gate.

Links

• DeepSeek Harness — the host this plugin runs in
• awesome-dsh-plugin — the curated list behind the DSH marketplace; GitHub topic dsh-plugin

License

MIT