ReAct Execution Pipeline Visualizer
Step 0 / 4
1.0s
A task has thought, action, observation and reflection phases. Each Step click advances one phase. Four advances normally complete a task. With an injected observation error, reflection clears the error flag and returns to thought; another four advances replay the task, giving eight. These bars share sixty pixels per phase advance. Thought, tool arguments and normal observations come from fixed preset records. The program does not call a model, weather service or interpreter. When the final preset task is finished, an additional advance marks the sequence completed and copies the stored final-success text. This is a scripted state-machine demonstration, not verification that the named real-world task succeeded. The source assigns forty percent of a task's token budget to thought, thirty to action and thirty to observation, rounding each separately. For an illustrative hundred-unit task, thought adds forty. A disabled tool blocks the action, adds fifty and returns the task to thought without selecting another tool. The bars compare forty with the fixed fifty penalty at six pixels per unit. Repeated clicks can keep adding the same thought charge and penalty; the log says it is reevaluating a fallback plan, but no new plan is generated. Allowed tool calls increase a counter rather than perform a real call. These assigned numbers should not be read as tokenizer output or an actual bill. The memory panel displays only the last window-sized slice of memory history. For an illustrative ten-record history, a four-record window gives forty-percent visible retention, while eight gives eighty percent, shown at five pixels per percentage point. Older records remain in the underlying array; the display is not compression, summarization or deletion. Empty history displays one hundred percent. Step Back changes the task index and phase but does not undo token counters, tool-call totals or memory entries. Reset clears those arrays and counters. Startup checks whether D3 is available and uses a fallback when it is absent, allowing later control bindings to run. The new video therefore needs separate preservation and playback evidence and does not claim real agent execution.