Introduction

DSH’s philosophy is “Everything is a plugin.” For agent developers, using Remotion for video isn’t just running commands in the terminal; it requires completing project diagnosis, composition discovery, still rendering, video rendering, and output metadata verification within the session.

chenjie1129/remotion-video-plugin is an independent community plugin that provides a structured Remotion workflow for DeepSeek Harness and registers five tools limited to the current workspace. It is maintained by chenjie1129 under the MIT license. This plugin is not an official project of DeepSeek or Remotion.

What is this

One-sentence definition: This is a Remotion video creation and verified rendering plugin for DeepSeek Harness.

The problem it solves: It enables DSH sessions to call Remotion projects in a checkable and reproducible manner, rather than relying solely on manual scripting or temporary commands.

It provides two types of capabilities:

  • A user and model-callable remotion-video skill.
  • Five workspace-restricted tools: remotion_doctor, remotion_list_compositions, remotion_render_still, remotion_render_video, and remotion_probe_output.

Core Features

Rule Modules and Templates

This plugin provides the remotion-video skill and includes eight focused rule modules.

It also contains three types of blueprints:

  • product-launch
  • vertical-captioned
  • data-story

Additionally, it contains ten bilingual model-to-render evaluation cases for model-to-render result verification.

Five Tools

Below are the responsibilities of the five tools:

Tool Responsibilities
remotion_doctor Diagnose package, entry point, CLI, ffprobe, and browser readiness
remotion_list_compositions Return registered composition IDs
remotion_render_still Render a PNG or JPEG still
remotion_render_video Render video and perform metadata probe
remotion_probe_output Return normalized media metadata

These tools work with output artifact cards containing workspace-relative paths, byte sizes, SHA-256 digests, and normalized media facts.

Release Evidence

This plugin distinguishes several types of evidence:

  • Unit and contract checks.
  • Real Harness probe.
  • Browser-backed integration.

A release is not declared as fully proven until the browser-backed integration workflow passes on the release commit. Probe-only success is not counted as a render-tool pass.

Installation and Enablement

Environment Requirements

Before using it, the following conditions must be met:

  • Node.js: ^22.19.0 or >=24.0.0
  • DeepSeek Harness host packages before 0.2.0: dsh-skill, dsh-tools, dsh-subprocess
  • A trusted Remotion project with its own project-local Remotion dependencies
  • Chrome/Chromium configured by the operator, or use Remotion-supported browser acquisition

Installation

Install the plugin into the web profile using the verified GitHub release tag installation command below:

dsh plugin --profile web add github:chenjie1129/remotion-video-plugin#v0.4.0

Configuration and Checks

After installation, you can first check the combined profile:

dsh --profile web --dump-config

If you need to configure a trusted browser for the tools, you can use a configuration item similar to the following:

- id: remotion-video-tools
  name: '@chenjie1129/dsh-remotion-video-plugin/tools'
  config:
    browserExecutable: /absolute/path/to/chrome-or-chromium
    browserMode: chrome-for-testing

Removal

To remove the plugin, you can uninstall the corresponding bundle:

dsh plugin --profile web remove @chenjie1129/dsh-remotion-video-plugin

Typical Usage

Standard Agent Session Example

You can start a standard-agent session and give a request similar to the following:

Create a 15-second 16:9 product-launch video. Diagnose the project, use frame-driven animation, render a representative still, then render and verify the MP4.

Tool Call Sequence

A common workflow is to perform diagnosis first, then discover compositions, followed by rendering stills and video, and finally checking the output:

  1. remotion_doctor: Confirm project, entry point, CLI, ffprobe, and browser availability.
  2. remotion_list_compositions: Get renderable composition IDs.
  3. remotion_render_still: Render a representative still.
  4. remotion_render_video: Render video and perform metadata probe.
  5. remotion_probe_output: Read normalized media metadata.

Development Checks

When developing or validating the plugin, you can run the following check commands:

npm ci
npm run check
npm run release:verify
npm run test:e2e -- --probe-only

These checks cover Node 22/24, real Harness/Remotion integration CI, and npm trusted-publishing automation.

Use Cases and Considerations

Suitable for developers who use DSH for agent workflows and wish to integrate Remotion rendering steps into the session toolchain.

Notes before use:

  • This plugin is an independent community plugin, not an official project of DeepSeek or Remotion.
  • Rendering will execute the JavaScript of the selected project and installed dependencies.
  • Tool paths are restricted to the current session workspace.
  • Commands use fixed parameter arrays.
  • Output replacement is opt-in.
  • Process output and props have boundary limits.
  • Cancellation will reach the managed process tree.
  • The plugin itself does not collect telemetry, store credentials, or upload media; however, project code, remote resources, or Remotion browser acquisition may still use the network.
  • The plugin is MIT licensed; Remotion has separate license terms, and users must verify them themselves.
  • The plugin usually runs under the current DSH process permissions; you should check the source code, dependencies, and license before installing.

Conclusion

The value of chenjie1129/remotion-video-plugin lies in organizing Remotion’s project diagnosis, composition discovery, still/video rendering, and output verification into a DSH-callable workflow and providing checkable release evidence.

GitHub repository:

https://github.com/chenjie1129/remotion-video-plugin

Verified materials do not provide a directory page URL, so this article does not provide an additional directory page link.