All plugins

DSH / BUNDLE / CLIENT-UI

dsh-agent-team-presets

v0.1.8bloodarea / dsh-agent-team-presets943d99d73e

InstallableBundlesUI & client pluginsCommunity · Topic auto-analysisWeb UI

Overview

dsh-agent-team-presets

Reusable Agent Team presets for DeepSeek Harness: a captain plus members with their own prompt, model, reasoning effort, and tools.

README / EN

Package documentation

Registry summary

Reusable Agent Team presets for DeepSeek Harness: a captain plus members with their own prompt, model, reasoning effort, and tools.

dsh.pub verifies the pinned bundle contract, runtime facts, and distribution semantics. The complete README remains in the source repository.

Read the full README on GitHub

LIMITATIONS

Known limitations

<a id="configuration-overridden"></a> ### Configuration writes are overridden If saving or selecting a Team reports: ```text Configuration for "agent-team-presets" is overridden by a home patch or command-line overlay ``` Check profile patches, `$DSH_HOME/cordis.patch.yml`, and `--patch` overlays for duplicate hand-written `agent-team-presets` declarations. Remove duplicate declarations while preserving Host-managed settings rows. ### Common issues | Symptom | What to check | |---|---| | Settings page is absent or plugin pending | Confirm profile type, peer dependencies, Agent Teams enablement, and client services. | | Skill deletion button is disabled | The skill is protected: inspect the blocker list in the modal (bound roles or dependencies must be unassigned first). | | Skill assignment refused (`dependency-missing`) | A required executable declared by the skill is absent from host `PATH`. Note that declared MCP servers are reported for visibility and do not block assignment; ensure MCP servers are configured in your profile. | | Member creation refused | Check storage domain availability, subagent execution backend (`spawn`/`fork`), model quota, and concurrency limits. | | Model route display mismatch | In Harness rc.2, `list_agents.model` reports fallback metadata. Verify actual routing via `spawn_team_member`'s `configuredRoute` or session `request/header` logs. | <a id="understand-the-implementation"></a>