How the Plugin Panel works

How the Plugin Panel works An architecture diagram generated by Archify. dshp-plugin-panel · itself a patch plugin · Architecture component dshp-plugin-panel itself a patch plugin Management view · face of the composition layer · Architecture component Management view face of the composition layer Skill capability · introduce = register · Session-level (agent context) Skill capability introduce = register MCP capability · mcp-client row · Session-level (agent context) MCP capability mcp-client row Host plugin · patch · hot mount · cordis.patch.yml · Process-level (host composition) Host plugin · patch hot mount · cordis.patch.yml Host plugin · bundle · cold mount · restart required · Process-level (host composition) Host plugin · bundle cold mount · restart required Skill pool · ~/.dsh/.skill-pool/local/ · Architecture component Skill pool ~/.dsh/.skill-pool/local/ Session introduce-set · .session-skills/<sessionId>.json · Session-level (agent context) Session introduce-set .session-skills/<sessionId>.json Frontend tabs · Skills / Plugins · Architecture component Frontend tabs Skills / Plugins exposes introduce / remove connect / disconnect toggle (hot) toggle (restart) presentation only register, no copy persist promote Session-level (agent context) Process-level (host composition) Legend Frontend Backend Database

Everything is a plugin

  • • Every capability is a loadable row in the DSH composition
  • • Skill = document capability, MCP = mcp-client row
  • • Host plugin = patch or bundle row

Two mount dimensions

  • • Session-level lives in the agent context, isolated per session
  • • Process-level host plugins load into the host and affect everything
  • • The Skills / Plugins split is presentation: one layer underneath

Introduce = register

  • • The registration points back at the pool folder; no file is copied
  • • Saved to <poolRoot>/.session-skills/<sessionId>.json
  • • Replayed when a resumed session comes back after a restart