Workflows

A workflow chains profiles into one reply. Each step runs in order and hands its reply to the next; only the last step answers in the chat. A “draft, then check against the canon” pipeline runs as a single message.

Workflows live in the Library. New workflow opens the editor.

Building one

1. Give it a Name.
2. Add a step and choose its profile. Each step keeps its profile’s model, temperature, rules and knowledge base.
3. Write Instructions for this step if the step needs more than its profile’s rules: “Write the next scene from the latest message”, “Check the text above against the canon and fix only what contradicts it”.
4. Choose what the step reads:
   • Use the workspace context: Memory, Worldbuild and retrieved lore. The profile’s own knowledge base is always included.
   • Read the chat history.
5. Reorder steps with Move up and Move down, and collapse them to see the whole chain.
6. Save workflow.

The first step reads your message. Every later step reads the reply of the step before it.

Running one

Allow the workflow in the workspace (Configuration › Profiles & Workflows), then pick it in the message box like a profile. Progress shows each step as it runs.

A step whose profile has no model shows A step has no model in the Library, and the workflow cannot run until it is set up.

When something goes wrong

• A step fails. The workflow pauses and asks: Retry the same request, Skip the step (its input passes on unchanged), or Interrupt and keep what the earlier steps wrote.
• A step writes a lot. If a step in the middle writes more than about 4,000 tokens, you can send it on as it is, or edit it first, so the next step is not flooded.

Tip

Steps can use different connections. A cheap fast model can draft, and a strong one can review, inside the same workflow.

Sharing

A workflow exports as one .klw file with every profile it uses and their knowledge bases. See Share profiles and workflows and the workflow recipes.