精选
为什么选中它
待人工精选——以下事实来自源码仓库。
它能做什么
Environment housekeeper for DeepSeek Harness: toolchain inventory, safe cache cleanup, and machine rules editor in the Web GUI settings.
适合谁
想用 DSH 获得这项能力的用户;装前建议先看源码和文档。
风险提示
- 未发现明显风险信号;安装前仍建议查看源码。
Environment housekeeper for DeepSeek Harness: toolchain inventory, safe cache cleanup, and machine rules editor in the Web GUI settings.
待人工精选——以下事实来自源码仓库。
Environment housekeeper for DeepSeek Harness: toolchain inventory, safe cache cleanup, and machine rules editor in the Web GUI settings.
想用 DSH 获得这项能力的用户;装前建议先看源码和文档。
dsh plugin --profile web add github:guo6x/dsh-housekeeper 作者没有声明支持的平台。
.tmp and cache directories agents leave behind: size / file count / mtime, 4000-file truncation markers, 30-day-untouched highlighting, click-to-expand content preview, check and delete - 🛡️ Whitelist protection — only project .tmp dirs and cache-root children are deletable; .. escapes, symlink escapes, and system paths are rejected, with a realpath re-check before every delete - 📝 Machine rules editor with a safety net — read/write ~/.dsh/AGENTS.md (the global rules every agent session loads), auto-backup of the previous version on every save, one-click restore, live on save - 🌍 Configurable — scan roots default per platform (Windows: D:\github / D:\environment\cache), editable in the panel, overridable via env vars - 🤖 Agent tools — housekeeper_report (inventory + disk report) and housekeeper_clean (same whitelist, max 10 paths per call) ## Install sh dsh plugin --profile web add dsh-housekeeper Restart dsh web, then Settings → Plugins → 环境管家. Requirements: DSH web profile, Node ≥ 22. ## Security model - All routes accept loopback clients only (403 otherwise) - Cleanup whitelist — a path is deletable only when ALL hold: - under <projects-root>\<repo>\ .tmp\, or a direct child of <cache-root>\ - normalized path stays inside the whitelist root (no ..) - realpath still lands inside the whitelist root (no symlink escapes) - the whitelist roots and repo dirs themselves are never deletable - The rules endpoint reads/writes $DSH_HOME/AGENTS.md only; the path is fixed - No telemetry, no external network calls ## How it works GUI settings ──fetch──▶ /housekeeper/state|clean|rules (loopback) ──▶ host plugin ├─ probe: candidate paths + PATH lookup + versions ├─ scan: rule-driven walk with sizes (4000-file cap) ├─ clean: whitelist + realpath check, then rm └─ rules: read/write $DSH_HOME/AGENTS.md (64KB cap) ## Develop sh pnpm install node build.mjs # esbuild → lib/index.js (host ESM) + lib/client.js (ModuleLoader bundle) node tests/core.mjs # 21 whitelist/scan/clean sandbox tests, no real environment needed MIT licensed. Issues and ideas welcome.不看 Star,人工一条条挑的。
把 DSH 的 settings.yaml 做成可视化看板:所有已注册的 settings namespace——包括官方界面从未覆盖的第三方插件配置——都渲染成可编辑表单。项目还早,但方向很对:告别手改 YAML。
给 DSH 的 DIY 轨迹可视化:把 agent 的计划与执行画成图,不用翻原始日志也能看清它在干嘛。项目还早,但补上了「一眼看懂 agent 在做什么」这个真实缺口。
从 Claude Code / Codex 把活派给 DSH:在宿主内拉起带分级预设的 DSH agent 会话,看原生子代理进度,还能借它的多模态桥给纯文本的 DSH 补上视觉和生图。编排型插件,把 DSH 变成其他编码 agent 的后端。