DSH Base
by DeepSeek
The official core profile bundle loaded first by every DSH profile.
CAPABILITY INDEX
Find developer-tool DSH plugins for dashboards, analytics, routing, observability, configuration, and workflow utilities.
by DeepSeek
The official core profile bundle loaded first by every DSH profile.
by DeepSeek
The official one-shot task bundle for running DSH without a browser or HTTP layer.
by DeepSeek
Hot Module Replacement Plugin for Cordis
by DeepSeek
Include files in cordis configurations
by DeepSeek
Timer service for cordis
by DeepSeek
Typert Remote Host dispatcher and Client API endpoint
by DeepSeek
Human-facing slash command for explicit session compaction
by DeepSeek
Log-only session feedback producer and human-facing slash command
by DeepSeek
File-backed settings provider (settings.yaml) for the DeepSeek Harness
by DeepSeek
Tool-independent managed DSH_* shell environment registry
by DeepSeek
Local-subprocess implementation of the DeepSeek Harness subprocess seam
by DeepSeek
Tool registry and execution pipeline for the DeepSeek Harness
by DeepSeek
Loader integration for generated Typert package contributions
by DeepSeek
Runtime registry for generated package reflection and Zod schemas
by DeepSeek
Abstract user-questions seam (ctx.userQuestions) for asking the human during agent runs
by DeepSeek
Abstract web access capability seam (ctx.web) for the DeepSeek Harness — search/fetch provider registry, registration-order-independent selection, request/result vocabulary, and the WebError taxonomy
by yjh051108
An experimental GitHub kit combining a runtime injector with task-aware reasoning-mode presets for DSH.
by lanlandeli
Token analytics with trends, activity heatmaps, model breakdowns and data exports.
DSH CATEGORY GUIDE
Developer-tool DSH plugins improve the surrounding experience with dashboards, usage analytics, routing, observability, configuration helpers, and workflow utilities. They often sit beside core task tools and can make a Harness setup easier to understand, debug, and maintain.
Compare the data collected, storage location, UI integration, supported Harness version, runtime overhead, export options, and maintenance activity. A dashboard or analytics plugin should explain whether it stores prompts, tool results, tokens, or only aggregate metadata.
Enable the minimum telemetry required and test the plugin with a representative workflow. Confirm how data is cleared or exported, whether a web interface opens a local port, and whether routing or configuration changes can be reversed cleanly.
FAQ / 02
Some only observe and display data; others change routing, configuration, or runtime behavior. Check the capability list and rollback instructions instead of assuming every dashboard is read-only.
Prefer the smallest dataset that answers the operational question. Aggregate token, timing, and failure metrics are often enough; prompt or response bodies require a stronger reason and clearer retention controls.