Environment housekeeper for DeepSeek Harness: toolchain inventory, safe cache cleanup, and machine rules editor in the Web GUI settings.
Pending human review — the facts below come from the source repository.
Environment housekeeper for DeepSeek Harness: toolchain inventory, safe cache cleanup, and machine rules editor in the Web GUI settings.
Users who want this capability in DSH; check the source and docs before installing.
dsh plugin --profile web add github:guo6x/dsh-housekeeper No supported platforms were declared.
.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.Not by stars — picked by hand, one at a time.
A visual settings dashboard for DeepSeek Harness: every registered settings namespace — including third-party plugin ones the official UI never covers — rendered as editable, schema-driven forms. Early, but the right direction: stop hand-editing YAML.
A DIY trajectory visualizer for DeepSeek Harness: watch the agent’s plan and execution unfold as a graph instead of scrolling raw logs. Early, but it fills a real gap — understanding at a glance what the agent is doing.
Dispatch DSH work from Claude Code / Codex: spin up in-host DSH agent sessions with per-tier presets, watch native subagent progress, and borrow a multimodal bridge that lends the text-only harness vision and image generation. An orchestration plugin that turns DSH into a backend for other coding agents.