Workflow & Ralph
Run model-authored orchestration workflows and the fixed fresh-agent Ralph workflow.
On this page
Many official DSH packages are already shipped in the Standard preset or host runtime. Check the install status below before adding dependencies or editing a composition.
Install and usage entry
No download needed for Standard
The Standard agent preset already mounts the model-facing capability. Do not install a duplicate copy just to make the tool appear.
Where you use it
Standard preset → ask for a workflow or Ralph task when orchestration is actually useful; inspect the resulting files and commands.
What it does
@deepseek-ai/dsh-tool-workflow
Related official packages: @deepseek-ai/dsh-workflow-worker-thread · @deepseek-ai/dsh-tool-ralph
- tool-workflow exposes general workflow execution to the model.
- workflow-worker-thread executes workflow scripts in worker threads.
- tool-ralph exposes the fixed fresh-agent Ralph workflow.
Is it already enabled?
The official Standard preset already loads a worker-thread workflow provider, tool-workflow and tool-ralph.
Configuration example
Use this as a reference when editing a custom Cordis composition. Installing a dependency does not by itself guarantee the plugin is mounted; the composition still controls what runs.
- id: workflow-worker-thread
name: '@deepseek-ai/dsh-workflow-worker-thread'
config:
provider: spawn
- id: tool-workflow
name: '@deepseek-ai/dsh-tool-workflow'
- id: tool-ralph
name: '@deepseek-ai/dsh-tool-ralph'
config:
subagentProvider: spawn
maxRounds: 64How to verify it
- Use a Standard-preset session and confirm workflow tools are present.
- Start with a small multi-step repository task whose result is easy to inspect.
- Review the produced files and commands rather than treating workflow completion as proof of correctness.
Limits and boundaries
- Worker threads isolate workflow execution from the host event loop but are not a security boundary.
- Workflow behavior still depends on the configured subagent provider and permissions.
- Ralph has its own fixed workflow policy; it is not a synonym for arbitrary workflow execution.