FolioDrop Publish for DeepSeek Harness

Publish user-approved agent output as a stable FolioDrop URL from DeepSeek Harness. The plugin registers one model-facing tool, foliodrop_publish, and keeps the FolioDrop API key in the Harness credential seam.

Scope

The first release is HTML-first:

• Complete HTML is published without rewriting.
• Markdown, text, JSON, code, and SVG are converted into a portable, self-contained HTML page.
• The plugin does not read arbitrary local paths and does not claim to be a generic binary file host.
• Search indexing defaults to off and requires explicit consent.
• Every publish asks for user approval because it uploads content and creates an externally reachable URL. Ordinary profile configuration cannot disable this gate.
• The publish origin is fixed to https://foliodrop.app; the credential is never sent to an operator-configured host.

Installation

Install the tagged plugin source directly from GitHub:

dsh plugin --profile web add github:jaxxchen003/foliodrop-dsh-publish#v0.1.0
dsh --profile web --dump-config

The same release is also available as a pre-packed artifact:

dsh plugin --profile web add https://github.com/jaxxchen003/foliodrop-dsh-publish/releases/download/v0.1.0/foliodrop-dsh-publish-0.1.0.tgz

From a FolioDrop source checkout, use the local package instead:

From this repository:

dsh plugin --profile web add ./integrations/deepseek-harness
dsh --profile web --dump-config

When the package is also available from npm, the equivalent registry command will be:

dsh plugin --profile web add @foliodrop/dsh-publish

The package ships plain ESM JavaScript, so installation does not execute a prepare or other lifecycle build script.

The plugin package is distributed under the MIT License. This package-local license does not change the license of the FolioDrop application outside this directory.

Credentials

Create a personal key at https://foliodrop.app/settings/apikeys, then store it as FOLIODROP_API_KEY through the DeepSeek Harness credentials UI/provider or in the process environment:

export FOLIODROP_API_KEY='fd_...'
dsh --profile web

The bundle configuration stores only the credential reference. The secret is resolved for each publish operation and is never included in tool output.

Tool behavior

Ask the agent to publish content explicitly, for example:

Publish this Markdown release note to FolioDrop as a visible work. Do not allow
search indexing. Return the share URL.

The tool accepts:

• content and content_type
• title, description, and optional code language
• visibility (visible by default or hidden)
• search_indexing_consent (false by default)
• optional source_model

Successful output includes the FolioDrop work id, slug, absolute share URL, visibility, transformed format, byte size, and the fixed source attribution DeepSeek Harness.

Compatibility contract

This release is tested against DeepSeek Harness 0.1.0-rc.6. Harness is in developer preview, so an upgrade must re-verify all four integration seams:

• defineTool registration and output validation
• ctx.credentials.resolve('FOLIODROP_API_KEY')
• the tools/pre-execute approval waterfall
• approval/request failing closed without an answerer

The rc.6 profile installer can report missing peer warnings from @deepseek-ai/dsh-tools; the release gate therefore verifies both the composed bundle with --dump-config and a real runtime boot, not installation exit code alone.

FolioDrop stores sourcePlatform: DeepSeek Harness on the work, so views can be aggregated by publishing source. This release does not yet implement a separate DeepSeek-specific referral or signup funnel.

Verification

pnpm --dir integrations/deepseek-harness install --frozen-lockfile
pnpm --dir integrations/deepseek-harness test
npm pack --dry-run ./integrations/deepseek-harness