v0.1.5
Added
-
Bundled
browser-use-cliskill: script-mode browsing through the ordinary
shell tool. The agent pipes Python to thebrowser-useCLI (audited at
0.13.8 / browser-harness 0.1.9), so every browser action rides existing
command approval instead of adding a new tool surface. The skill defaults to
an isolated throwaway-profile browser, mandatesANONYMIZED_TELEMETRY=false
(which also disables default vendor cloud sync), forbids private-network and
cloud-metadata navigation, forbids automated MFA entry and vendor cloud
browsers, and permits attaching to the user's logged-in Chrome only through
Chrome's own per-session consent popup. -
Skill forge:
skill_control prepare_savedistills a session-verified
procedure into a durableSKILL.md, and/omd-distill [focus]queues a
drafting turn. Saves flow through the proposal plane — the proposal carries
the exact before/after file content and secret-content warnings, and only an
approvedproposal_control applywrites the file (atomic temp+rename,
containment-checked after path resolution, SHA-256 stale guard against
concurrent edits, symlinked targets rejected). Scopeprojectwrites
<workspace>/.dsh/skills/<slug>/SKILL.md, scopeuserwrites
$DSH_HOME/skills/<slug>/SKILL.md; the upstream skill watcher picks new
files up live. Content bounds: slug ≤ 41 chars, single-line description
≤ 500 chars, body ≤ 32 KiB. -
Plugin control and its curated organ bank:
plugin_controllists and inspects
exact-pinned entries, then prepares session-scoped load/unload proposals.
Discovery and proposal preparation import no plugin code; approved load
rechecks the installed version and reviewedname/provide/inject
manifest beforeagent.ctx.plugin()mounts it. Unload and agent teardown
await Cordis effect reversal. Arbitrary packages and runtime installation
are unrepresentable in v1. The first bank entry is the upstream
dsh-skill-badge@0.1.0-rc.6. -
Capability discovery plane:
capability_searchand/omd-capabilities
search model-visible tools, skills, slash commands, MCP servers, and curated
session plugins through stable refs (tool:…,mcp:…,plugin:…). Hits
return status and an exact next action; activation still requires the
existingmcp_control/plugin_controlprepare path plus an approved
proposal_control apply. Discovery itself never starts processes, imports
packages, expands credentials, or creates proposals.