Workflow system

Jarvis workflows follow a consistent cycle: understand, plan, execute, verify, remember. The UI shows the live thinking timeline and execution logs throughout the run.

Planning

The planner breaks a command into steps with tool hints and risk levels. Users can preview the plan before execution.

Execution engine

Steps are routed to tools such as memory, website generation, code generation, file actions, browser control, app launcher, automation routines, and terminal diagnostics.

Pause, resume, cancel

The execution control system checks state between steps. Pause holds the workflow, resume continues it, and cancel stops it cleanly with a logged message.

Self-healing

If a step returns a failure pattern and the verification layer considers it retryable, Jarvis logs the issue and tries again with the same tool path.

Recorder

The workflow recorder captures real agent and browser actions while active. Stopping the recorder saves a JSON workflow under the local memory folder.

Replay

Replay re-runs recorded agent steps. Browser events are retained as history and can be expanded into deeper replay actions as the operator evolves.