Studio
The Task Builder
Author what the bot does as a visual flow — no code.
The Task Builder edits a task's flow — a tree of steps the bot runs top to bottom. You reach it by opening a task (or New task) from the Studio library. It's a power-user surface; this page tours it at a glance rather than documenting every step.
- Basic / Configurable switch
- Expand · Config · Save task
- Palette: step categories
- Flow: files row + block stack
- Inspector: step options
Three columns
- Palette (left) — the steps you can add, grouped by category. Click one to insert it into the active slot.
- Flow (centre) — a row of flow files (Root plus any named functions you add), a breadcrumb showing where new steps land, then the flow as a stack of blocks. Reorder with ▲ ▼, remove with ✕, and nest steps under control blocks.
- Inspector (right) — the selected step's parameters.
The step palette
Steps are grouped into Capture, Perception, Action, Control, Composition and Scheduler. Control steps (If / Else, loops, Retry block, For each match) are containers with their own slots — an If / Else has a Then and an Else. New function names a reusable sub-flow you can call from anywhere in the task, and Run routine calls a shared library routine.
The inspector
A step that produces a value exposes a typed Store … as binding, naming a variable later steps can read. A condition (on an If or Loop until) picks a variable that is actually in scope at that point, an operator drawn from the variable's type, and a value to compare.
Test it: Run flow
Run flow runs the task once against a chosen emulator while you watch, streaming to the Log tab. The Test inputs tab mocks the per-instance settings form so your picks feed the flow's config variables, and Expand pops the whole work area into a large window for complex flows.
Config: how the task runs
The Basic / Configurable switch decides whether the task carries a per-instance settings form (built on the Config UI tab). The Config button opens Task config: the run shape (Finite — does its job once and stops, or Loop — repeats until you stop it), whether it reports units toward a goal, whether it's a background watcher, how many marches it uses, its Requires buildings (City Mapper gate), the default schedule a plan inherits, and — for bundles and routines — its Call options and Returns. Save task stores the name, type, run role and description.