Skip to content

Releases

v0.1.2 — bulk selection, updater fix, discovered plugin caches / 批量选择、更新器修复、插件缓存自动发现

Choose a tag to compare

@you112358 you112358 released this 20 Nov 09:22

v0.1.2 — bulk selection, real updater cleanup, discovered plugin caches / 批量选择、更新器缓存修复、插件缓存自动发现

Features

  • Select all / deselect all in the cleaning list, with a live {n}/{m} selected counter. Select-all only includes rows that actually hold data, so an empty page cannot select nothing by accident.
    • 清理列表新增「全选 / 全不选」,并实时显示「已选 n/m 项」。全选只会选中真正有数据的行。
  • Plugin caches are one generic target now. They are discovered from the active profile: a plugin can declare dsh.cache in its package.json (string, array, or { path, mode }), and conventional cache directories (cache, .cache, compile-cache, logs, tmp) next to a plugin's data roots are picked up automatically. New options pluginCacheDiscovery (default true) and pluginCacheExtraPaths. No per-plugin adapter table.
    • 插件缓存改为通用项:从当前Profile自动发现,支持插件在自己的 package.json 里声明 dsh.cache,也会识别数据目录旁的常规缓存目录。不再内置任何插件适配表。
  • New terminal helper node scripts/clean-cli.mjs cleans the same targets from a terminal — the escape hatch for caches the running desktop client keeps open.

Fixes

  • The updater download cache can be cleaned. Its unit pointed at its own allow-listed root, so the safety fence refused every deletion while the row still looked cleanable. Roots listed in CLEANABLE_ROOTS may now be emptied in contents mode, and locked files get four attempts (80 ms, then 200 ms) before being reported.
    • 更新器下载缓存现在可以正常清理:此前它指向自己的允许根目录,安全围栏拒绝删除所有内容。
  • Caches held open by the running client are reported as in use, not as errors. Chromium keeps the network cache journal open while the desktop client runs, so a row can honestly only be cleaned after the client quits. Those entries now show a dedicated note, are excluded from the error count, and the tool prints a separate "held open by the running client" section.
    • 被运行中客户端占用的缓存不再计为错误:行内显示「被客户端占用」,清理报告不再统计它们。
  • The clean report banner no longer repeats a "skipped" count for rows that already explain themselves.
  • row.restart was always undefined in clean results; it is now carried through so the "restart to reclaim" hint works.

Removed

  • The dsh-session-projections target (cleaning it caused display problems). The id now returns UNKNOWN_TARGET; 11 targets remain.

Docs

  • Both READMEs updated: 11-target table, dsh.cache plugin cache discovery, the in-use caveat with the CLI, new configuration keys.
  • CI now also runs the safety fence, plugin-cache discovery and real-cleanup checks.

Upgrade

# in DeepSeek Harness
plugin_manager action=remove_bundle   target=dsh-cache-cleaner
plugin_manager action=install_bundle  target=/path/to/dsh-cache-cleaner

or toggle the plugin row off/on in Settings → Plugins, then refresh the page (the client bundle is served with a new revision).

v0.1.1 — rescan fix / 重新扫描修复

Choose a tag to compare

@you112358 you112358 released this 18 Nov 17:03

v0.1.1 — rescan fix / 重新扫描修复

Fixes

  • Rescan no longer collapses to the 7-day filter. The Rescan button passed its click event into the age-mode argument, so every rescan ran with olderThanHours: 168 no matter which mode was selected. Caches written within the last week then came back as 0 B and every row looked empty. The button now re-scans with the mode shown on the page, and only 'week' / 'all' are accepted as mode values.
    • 点击「重新扫描」时不再误用 7 天过滤。此前按钮把点击事件当成了模式参数,导致无论选哪个模式都按 168 小时扫描,于是所有行都显示「无缓存」。
  • The settings page opens in Everything mode so the inventory is visible on first load; Only a week old stays a deliberate, conservative choice.
    • 设置页默认打开「全部缓存」模式,首次进入即可看到完整清单;「仅 7 天前的」仍是主动选择的保守模式。

Improvements

  • Scan results now carry freshBytes / freshFiles per target and in totals, so skipped recent caches are quantifiable.
  • The settings page labels recently written caches as 近期写入 {size},保留 / written recently, kept instead of “no cache”, and explains why nothing is eligible when the week filter matches nothing.
  • The cache_scan tool output lists X kept per target plus a total line for recently written bytes kept by the age filter.

Upgrade

# in DeepSeek Harness
plugin_manager action=remove_bundle   target=dsh-cache-cleaner
plugin_manager action=install_bundle  target=/path/to/dsh-cache-cleaner

or toggle the plugin row off/on in Settings → Plugins, then refresh the page (the client bundle is served with a new revision).

v0.1.0 — first public release / 首个公开版本

Choose a tag to compare

@you112358 you112358 released this 18 Nov 15:06

dsh-cache-cleaner v0.1.0

First public release. A DeepSeek Harness plugin that finds and removes the
rebuildable caches of DSH itself, its desktop client, and the plugins installed
into a profile — with a settings page, two agent tools, and an HTTP route that
all run the same cleanup engine.

What it cleans

13 targets in four groups (13 个目标,四组):

Group Targets
DSH core request-image cache, session projection cache, prepared-shell spill
Temp spill dsh-subprocess-*, dsh-spill-*, other dsh-* temp entries
Desktop client HTTP cache, Code Cache, GPU/shader caches, logs
Plugins & updater updater installer cache, plugin context overview cache, cc-safety-net build cache

On the author's machine the first launch reported 1.5 GB / 1213 files, of
which 8.8 MB / 202 files was older than a week.

Entry points

  • Settings → 缓存清理 / Cache Cleaner — rescan, review per-target sizes and
    paths, tick a subset, confirm with a second click.
  • Agent tools — cache_scan and cache_clean (olderThanHours), so an
    agent can plan a cleanup before running it.
  • HTTP route — POST /dsh-cache-cleaner/api/{scan,clean}, same-origin and
    authenticated through the host's connection trust checks (untrusted requests
    are answered 401).

Cleaning options

Option olderThanHours Meaning
仅 7 天前的 / 7+ days old 168 only entries untouched for the last week
全部缓存 / Everything null every entry, including caches written seconds ago
default omitted per-target cutoff (temp targets keep entries newer than 6 h)

Install

The package is installed by link, not from npm:

git clone https://github.com/you112358/dsh-cache-cleaner.git

then, in a DSH session:

plugin_manager action=install_bundle target=<absolute path to the checkout>

The settings page appears under Settings → 缓存清理 / Cache Cleaner; refresh the
page once after installing. Uninstall with
plugin_manager action=remove_bundle target=dsh-cache-cleaner.

Safety

  • Only declared roots are touched (~/.dsh, the OS temp directory, the desktop
    client's userData, the updater directory, ~/.cc-safety-net); sessions,
    attachments, profiles, credentials and client Local Storage are explicitly
    protected.
  • Symlinks are never followed. Files held open by the running process are
    reported as skipped, never forced. Deleting a cache only costs a rebuild.

Checks

node --check client/client.js, a host-half import probe, and
node scripts/check-client.mjs run in CI on Node 22.

Full Changelog: https://github.com/you112358/dsh-cache-cleaner/commits/v0.1.0