Skip to main content

Projects and Steps

The word “step” may make you think of stages that things flow through in order. The steps on which you place registered agents in a project are different.

This page explains what a step is, how registered agents are placed, and what is handed over between steps. The setup procedure is in the Agent Guide.

A project is the unit that gathers how a task is carried out​

A project is the set of things for carrying out one task. You line up steps in it and place registered agents on the steps where you want work done.

It is not only steps and agents that are gathered. How much to delegate (the run rules), who takes part, and which connectors are used are also decided per project. Records also accumulate per project.

A step is a place for registered agents​

A step is a place to put registered agents. The step itself does nothing. The registered agent placed on it does the work set by its container image (and, in a workflow, by the contract the administrator registered). A workflow has two kinds of step where no agent runs, though: the review step, where a person decides, and the Branch step, which chooses the lane to follow from the result of the previous step. The Marketplace edition has no “External automation” step that sends to a chosen destination.

The order in which steps are lined up is not always the order of processing. A workflow proceeds in step order (at a Branch step, only the chosen lane is passed through). In a cycle, you set a sweep period for each agent placed on a step, and each runs on its own period. Which of the two applies depends on the type (Cycles and Workflows).

Agents and steps are not one-to-one​

A registered agent is not part of a step. It is an independent thing the administrator registered, and you can place the same registered agent on several steps.

Each time a registered agent is placed on a step is called a placement. The step settings, and the sweep period of a cycle, are per placement. Place the same agent on two steps and there are two placements, each with its own settings values and connectors.

What happens when several are placed on the same step​

In a workflow, the agents of the same step run one at a time in placement order. There is no “Run at the same time”. In a cycle there is no waiting for one another; placements on the same step also run on their own periods or webhooks.

In a workflow, the previous step's output is not passed to the next step automatically. What is passed is only the files you connected in the step settings' “Input file handover”. Always connect any output you want to hand across steps (Agent Guide). In a cycle, outputs are not passed between steps.

No agent runs on a step where a person decides​

No agent runs on a review step. A review step belongs to workflows and cannot be placed in a cycle. The reviewer looks at the case's artifacts and settings and chooses to proceed, send back, or reject. It is a step for judgment, not a step where an agent does something. If you set the kind of review to “Manual work”, it can also be a step where AI does not run and a person does the work before proceeding.

Where to put a review step and how to choose reviewers are covered in the Review Guide.

How an agent behaves is settled by its image and contract​

The Marketplace edition has no Playbooks and no Skills. You do not attach goals (instructions) or guardrails either. What a registered agent does is settled by its container image (and, in a workflow, by the contract the administrator registered). No text of instructions is passed from the project to the agent. What the project decides is which step it is placed on, and the settings per step.

This attribution matters later. Changing step settings does not change the agent's image. To change what the agent does, the agent's developer rebuilds the image (an agent placed in a workflow is certified again by the administrator) (Agent Guide). The change also reaches other projects that use the same registered agent, from the cases that start next (a case that has already started keeps the content it started with).

There is no project memory​

The Marketplace edition has neither project memory nor company memory. Decisions and conditions are not carried over automatically from one run to a later one. What is handed between steps is files. Decide what you want to keep for the next run through the agent's output and its contract.

  • Cycles and Workflows — Types in which step order matters, and types in which it does not
  • Agent Guide — Place a registered agent and enter step settings
  • Review Guide — Where to put a review step and who decides