Documentation Index
Fetch the complete documentation index at: https://docs.cyberdesk.io/llms.txt
Use this file to discover all available pages before exploring further.
Why it’s useful
- Iterate safely without touching the original workflow
- Branch into a new workflow and riff from a solid baseline
- Merge improvements back only when you’re confident
- Optionally carry over trajectories for faster replay
How to use it
- Open a workflow, click the three‑dot menu in the top‑right, then click Duplicate.
- Edit and test the copy.
- If you want a new workflow, keep iterating on the copy and you’re done.
- If you want to merge back, open the copy and click Merge Workflow.
- Choose the target (usually the original), decide whether to copy generated trajectories, and confirm the merge.
How it works
- Duplicate creates a new workflow with the same prompt, schemas, post-run checks, settings, and tags. Prompt images are copied to new storage paths so the copy is independent. If you opt in, generated trajectories are duplicated onto the copy with fresh trajectory images and remapped prompt-image references.
- Merge updates the target workflow’s prompt, schemas, post-run checks, settings, and tags from the source. The target name stays the same. This is a replace-to-match merge for workflow configuration, not a union.
- If you duplicate a workflow, add new post-run checks on the copy, and merge it back, those new checks come over because the copy already contains the original checks plus your additions. Target-only post-run checks on the destination do not survive unless they also exist on the source.
- Before the overwrite, merge saves the target’s current name, prompt, schemas, terminal command allowlist, and post-run checks in version history. If you opt in, generated trajectories are duplicated with new images. The source workflow is then deleted asynchronously.