The current step of a running execution

While an execution runs, its card on the Executions screen tells you what it is doing right now. The card's Step row names the execution's current step beside the elapsed time: it sits right under the Start field, which counts how long the execution has been running. Together they say what the execution is doing and how long it has been at it. The rest of the card is described in the list of active executions.

Where the step comes from

The step follows the execution's own events. It is the latest entry of the execution's events timeline, such as a tool the AI tool started, with the command it runs or the file it reads or edits, the tests the execution is running, or a step the session reported. As each new event arrives, the step changes to follow it. The AI tool's raw output is not a step: it stays in the execution's output.

While the dashboard holds none of the execution's events — before the first one reaches it, or after you open the dashboard on an execution already running, until it receives one — the card shows the step HarmFlow itself reports for the execution instead, such as:

The language of the step

A step HarmFlow names itself, such as starting an AI tool, is written in the language of the interface: with the interface in Portuguese, the card reads "Iniciando Claude Code" rather than "Starting Claude Code". What the AI tool wrote, the commands it runs, and the paths of the files it touches appear as they are, never translated.

Before the first step

An execution that has no step yet, neither an event nor a step HarmFlow reports, shows "Waiting for the first step…" in its Step row until the first one arrives.

Why there is no percentage

The card never shows a percentage, a progress bar, or any other measure of how much of the work is done. An AI tool's session has no known length: how many steps it takes depends on what it finds along the way, so nothing could say honestly that it is halfway through. Rather than invent a number, the card shows what the execution is doing and how long it has been running.

The thin line under the step sweeps across, again and again, while the execution is active. It shows that the execution is at work; it never fills up and measures nothing.