dsh-profile-settings

The stock DSH harness exposes a single global settings.yaml as the only configuration seam, which makes it painful to run several agent workflows side by side that need different temperatures, tool sets, or system prompts. dsh-profile-settings adds a per-profile overlay file (profiles//settings.patch.yml) on top of that baseline: object sections merge recursively, arrays and scalars replace wholesale, and the !unset directive explicitly deletes an inherited value. Each profile declares only the fields it cares about; everything else falls back to the global layer automatically, keeping profiles independent.

Existing plugins see no behavioral change: ctx.settings reads and writes, official schema validation, expectedRevision conflict detection, and watcher events all work exactly as before. In-process writes land solely in the profile overlay; replace({}) re-inherits the global layer rather than the composition default. The Web UI gains a Profile Settings panel where every field carries a source badge (Default / Composition / Global / Profile / Masked) plus set, unset, mask, unmask, promote, and reset actions, all routed through a loopback RPC channel with no extra session context. On hot reload, temporarily invalid YAML is retained at the last good value with a warning; at boot, unresolvable profiles, !unset inside an array, global and overlay pointing at the same file, or a duplicate ctx.settings owner all fail loud.

It is built for teams or individuals who maintain multiple agent workflows in a single DSH harness—say a high-temperature creative-writing profile next to a conservative SQL-generation profile. All profiles share one global baseline, override only their differences, pick up edits instantly via hot reload, and rely on writer locks with atomic renames for cross-process file integrity.