TachiBot/Docs
HomeGitHubnpm
IntroductionInstallationQuick StartExamplesTools OverviewPlannerPrompt TechniquesWorkflowsPingPongTool ProfilesTools ConfigThemesUsage StatsAPI KeysWhat's NewTerms & ConditionsCookie Policy
Products
TachiBot MCPdokorotachi-agent
Getting started
  • Introduction
  • Installation
  • Quick Start
  • Examples
Core features
  • Tools Overview
  • Planner
  • Prompt Techniques
  • Workflows
  • PingPong
Configuration
  • Tool Profiles
  • Tools Config
  • Themes
  • Usage Stats
  • API Keys
Resources
  • What's New
Legal
  • Terms & Conditions
  • Cookie Policy

Loading documentation...

← Previous
Prompt Techniques
Next →
PingPong
Edit this page on GitHub
Docs/Core features

Workflows

Chain tools into multi-step orchestrations with YAML or JSON. Pass outputs between steps, run in parallel, debate for rounds.

Basic structure

basic-workflow.yamlyaml
1name: my-workflow
2description: What this workflow does
3version: "1.0"
4
5settings:
6 optimization:
7 enabled: true
8 smartRouting: true
9
10steps:
11 - name: step-name
12 tool: tool_name
13 input:
14 param1: value1
15 output:
16 variable: variable_name
17
18output:
19 format: detailed

Workflows vs agent chaining

Simple chaining runs one step after another. A TachiBot swarm runs models in parallel, then synchronizes, debates and synthesizes.

  1. Parallelstep 1
    Model AModel BModel CModel D
  2. Synchronize all outputs
  3. Deep collaborative reasoning5 rounds
  4. Adversarial debate3 rounds
  5. Final synthesis

Where to define workflows

workflows/
Recommended default — a plain folder.
.tachi/workflows/
Alternative hidden config location.

Reference earlier outputs with ${step_name.output}.

Workflow tools

workflow
Execute a YAML workflow.
workflow_start
Begin a session with variables.
continue_workflow
Resume an interrupted session.
validate_workflow
Syntax, tool registry, dependency graph.
visualize_workflow
Render the step graph.
create_workflow
Requires overwrite: true to replace an existing file.