Build workflows
Type /workflow in the composer to run a multi-phase workflow template instead of a single prompt. Phases run in order (seed, analyze, verify, judge, synthesize), phases can fan out to several agents, and each phase can use a different provider.
Type /workflow in the composer to run a multi-phase
workflow template instead of a single prompt. Phases run in order
(seed, analyze, verify, judge, synthesize), phases can fan out to
several agents, and each phase can use a different provider. A failed
phase agent retries once on the same slot; you can also retry it from
the transcript. The Agents
panel shows every phase and worker settling in real time. You can write
your own templates in the composer.
Workflow editor drafts survive moving between templates. Closing a dirty editor asks whether to keep editing or discard. A successful save is retained even if refreshing the template list fails, so retry does not create a duplicate workflow. A true save failure keeps the unsaved draft available.
A workflow can live in the repo. When you run the default template,
Solenta reads WORKFLOW.md (or
.solenta/workflow.md) from the thread's checkout, so
the workflow versions with the branch. An invalid file fails the
start with its name in the error. A template you pick explicitly
still wins. Export to repo in the workflow editor
writes a template out as that file and asks before overwriting.
A multi-phase run that was cut off by a crash or quit is kept. Retry on an interrupted agent reruns the interrupted agents of that phase and continues from there; finished phases are not redone.