Read product-facing context
Use README files, public docs, changelogs, package metadata, landing-page copy, and selected screenshots or clips.
Developers / DeepSeek Harness
Public DSH plugin · Developer preview
Create launch-video angles from DeepSeek Harness.
Use the repository context already in your DSH workspace to shape three Angles launch-video concepts, choose the strongest story, and render only after confirmation.
Pinned install
dsh plugin --profile demo add github:anglesvideo/anglesvideo-dsh-plugin#d0527be50716a208b57a0d1ddbc64a846ace1d31No raw repository upload · Three concepts first · Explicit render confirmation
dsh / angles-launch-video
Context boundary
read README.md
read docs/public
read CHANGELOG.md
skip .env
skip customer-data
Agent response
01 · Pain angle
02 · Workflow angle
03 · Proof angle
Built for DSH sessions
Repository boundary first
Human confirmation before render
Workflow
A plugin-shaped path from repo context to MP4.
DeepSeek Harness is a strong fit because launch-video creation is not a single prompt. It is a sequence of visible decisions.
Prepare a structured brief
Convert repository context into audience, pain point, promise, proof, use case, and launch constraints.
Review three angles
Compare distinct hooks, narratives, scene plans, media requirements, and recommended Angles templates.
Confirm the render
Render only after a human chooses the concept and explicitly confirms that Angles should create the MP4.
Prompt shape
Ask for concepts, not an immediate render.
The first DSH workflow should make the agent produce reviewable launch directions before it calls any render endpoint.
Create a 30-second product launch video for this repository.
Read only product-facing context: README, public docs, changelog,
package metadata, landing-page copy, and screenshots I provide.
Before rendering, show me three distinct launch angles with target viewer,
hook, narrative, recommended template, media needs, and claims to verify.
Do not render until I choose an angle and explicitly confirm.Target viewer
Opening hook
Narrative promise
Scene plan
Recommended template
Screenshot or clip needs
Claims to verify
Call to action
Safety boundary
The video needs product truth, not private code.
A useful launch video usually comes from README, docs, screenshots, changelog, and public positioning. Sensitive implementation data should stay out of the workflow.
Do not upload raw repositories to Angles.
Skip .env files, credentials, private keys, database exports, customer data, and production logs.
Send a structured product summary instead of unrelated implementation files.
Preview missing media or claim risks before spending a render allowance.
Status
Why this page says developer preview.
DeepSeek Harness is public, active, and plugin-native, but its own documentation marks the project as a developer preview. The Angles integration should ship with tested versions and pinned compatibility notes.
Official DSH positioning
DeepSeek describes Harness as a plugin-composable agent runtime where capabilities can be swapped or recomposed.
Open sourcePlugin discovery
Community projects are currently discoverable through the GitHub dsh-plugin topic.
View topicPinned compatibility
The Angles DSH bundle is public with a real repository, tested tool boundary, and pinned-commit installation path. Expect updates while DeepSeek Harness remains in developer preview.
View the Angles pluginFAQ
What is available now?
Is the Angles DeepSeek Harness plugin available today?+
Yes. The public bundle is https://github.com/anglesvideo/anglesvideo-dsh-plugin. It is an early integration for the DeepSeek Harness developer preview, so install a pinned commit and expect compatibility updates.
Why is the plugin still marked developer preview?+
DeepSeek Harness is plugin-native but its official documentation warns that compatibility-breaking changes may happen. The bundle is public and installable, but its README pins the tested DSH/runtime assumptions.
Will it send source code to Angles?+
The intended workflow sends a structured product brief, not a raw repository upload. Product-facing context is enough for launch-video angles, and sensitive files should stay local.
Can I build this through the API now?+
Yes. The Angles developer API already supports concept generation, templates, render preview, asset upload, render confirmation, and status polling.
Build the workflow today through the Angles API.
Concept generation, template metadata, render preview, asset upload, confirmed render, and status polling are already available to authenticated developer workflows.