Distribute a Carefully Tuned Agent Harness with Profiles

The core value of a Profile is simpler distribution

A Profile is more than a package of files. Its more important job is to turn an Agent Harness that once required a developer to explain and rebuild step by step into a versioned unit that can be delivered directly.

A Plugin distributes one capability; a Profile distributes the complete experience an author has already tuned and verified. The author handles runtime selection, Plugin composition, load order, and configuration complexity once. Recipients do not need to understand dependency resolution, Cordis patches, or internal loading mechanics.

After the basic DSH and CLI setup, nontechnical collaborators in product, operations, or research can use the same Agent Harness through one explicit version and one command. This transfer of expert work into low-friction distribution is the key differentiator of Profiles.

What a Release locks

To make distribution trustworthy, every Release records an exact DSH runtime, author-confirmed bundle order, exact npm versions or GitHub commits, Cordis patches, local input contracts, verification evidence, and a content hash. A published version remains immutable.

Input contracts contain only environment-variable names and their purpose. API keys, tokens, and other values are never uploaded. The content hash identifies the complete Release, not just one Plugin.

{
  "schemaVersion": 1,
  "version": "1.0.0",
  "name": "Web Workspace",
  "runtime": { "version": "0.1.1-rc.2" },
  "bundles": [
    { "packageName": "@deepseek-ai/dsh-base", "version": "0.1.1-rc.2", "sourceKind": "builtin" },
    { "packageName": "dsh-better-sidebar", "version": "0.15.0", "sourceKind": "npm" }
  ],
  "inputs": [{ "key": "DEEPSEEK_API_KEY", "label": "DeepSeek API key", "required": true, "secret": true }],
  "contentHash": "sha256:ac88d34a1e82dfc01e6908edb157caee27f4b21e349dc922d9babd864dc043dd",
  "publishedAt": "2026-08-22T00:00:00.000Z"
}

Discover and inspect a Profile

Authors can share a direct Hub Profile link and a Release version. Recipients can also browse public Profiles at /profiles or search by use case from the CLI. A detail page shows the runtime, bundle load order, exact Plugin versions, GitHub commits, patch count, and required local inputs.

Before applying a Profile, check its author, version, composition, and input requirements. Specify an exact Release version when reproducibility matters instead of relying on latest.

dsh-hub profile search web

# Public reference Profile
# https://dshpluginhub.ai/profiles/dsh-web-workspace

Preview first, then apply an exact Release

Recipients do not install and configure every Plugin themselves. A dry run resolves the complete Release and prints the commands and lockfile without changing the current Profile. One apply command installs the same exact version after review.

The CLI installs and validates in a separate staging Profile, saves the current revision, and only then switches the target Profile. Missing inputs or failed validation leave the existing environment untouched.

dsh-hub profile apply dsh-web-workspace --version 0.1.0 --profile web --dry-run

dsh-hub profile apply dsh-web-workspace --version 0.1.0 --profile web

Share an environment you have already verified

If you have already tuned a working local DSH Profile, capture and publish it from the CLI to deliver that result to other people. The CLI preserves the bundle order in package.json, reads installed exact versions, and checks for mutable GitHub references, local paths, and likely credential values.

You can also sign in to the Dashboard and use /dashboard/profiles/new to search indexed Plugins, arrange their order, declare the runtime and local inputs, and publish the same kind of Profile Release.

dsh-hub login

dsh-hub profile share my-team-stack --version 1.0.0 --profile web --display-name "My Team Stack"

History, rollback, and portable files

Before replacing an existing Profile, the CLI saves a revision. Use history to inspect local revisions and rollback to restore one, making Profile upgrades reversible.

A .dshprofile is a portable Release file. On import, the CLI validates the release.json schema and content hash before using the same staging, validation, and switch workflow.

dsh-hub profile history --profile web
dsh-hub profile rollback <revision> --profile web

dsh-hub profile import team-stack.dshprofile --profile web --dry-run

When to use a Profile

Install a single Plugin when you only need one independent capability. Publish a Profile when you want to deliver a complete, carefully tuned Agent Harness to teammates, customers, or community users.

Common uses include giving nontechnical teams an internal Agent, distributing customer solutions, standardizing team environments, sharing verified Agent tool stacks, teaching or demos, and new-device setup. A Profile distributes the composition and order; external service state, account permissions, and secrets still come from each local machine.