taoshi1999/dsh-workspace-hygiene

dsh-workspace-hygiene adds a Workspace tab to DSH web that manages the intermediate artifacts long agent tasks accumulate: a separate maintenance process classifies every workspace file as protected / valuable / intermediate / disposable / uncertain, shows a cleanliness score, and proposes names, directories and removals with a directory tree, purpose summaries and confirmed organisation plan on the left and a dedicated hygiene-Agent conversation on the right, in Manual or Automatic (assessment plus consent, never unattended) mode.

dsh-workspace-hygiene manages the growing collection of intermediate artifacts (logs, code and scratch files) that long-running agent tasks accumulate, because repeatedly searching and interpreting them costs tokens and reasoning quality even though the files on disk do not. It adds a Workspace tab immediately after Trajectory with a two-column layout: the directory tree, file classifications (protected / valuable / intermediate / disposable / uncertain), purpose summaries, suggested paths and a cleanliness score stay on the left, while a dedicated hygiene-Agent conversation stays on the right with the primary composer hidden. It separates value assessment from action - keeping valuable files and useful intermediates with naming and directory suggestions, recommending removal for files that clearly have no further value, and leaving the action undecided for review when evidence is insufficient - and every proposed file action is confirmed or declined in an inline card before anything moves, with scanning, organisation, verification, review and rollback events surfaced in the fixed right-hand panel.

Workflow & Automation ★ 4
View on GitHub ↗

Install

dsh plugin --profile web add github:taoshi1999/dsh-workspace-hygiene#main

Copied verbatim from the README's 'Install or update' block. The README also documents a local-checkout form (dsh plugin --profile web add .).

Compatibility

The browser sends a session ID, never an arbitrary workspace root: the host derives the root from that live session and uses DSH's Connection RPC transport and trust checks, and an explicit workspaceRoot configuration can pin the deployment boundary. A separate maintenance process watches filesystem changes and periodically assesses the workspace, but Manual is the default and monitoring never moves source files or injects messages into the primary agent; Automatic means assessment plus a consent request, not unattended mutation. Symbolic links are listed but never traversed.

Details

Alternatives

940842546/dsh-permissions · adithya-hmt/fullstack-expert · alib8b8/dsh-plugin-aflare

More plugins in Workflow & Automation

Browse more in Workflow & Automation

Guides for Workflow & Automation plugins